Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f41c147b517655f6bc929a7f7aeb8f115aa625745fde655ceac424144e5890b3

Tx prefix hash: 51773ea48ea1976595a312fee9cff98638d194eeba1455cdb27e4dc343814904
Tx public key: e7c5cf12f60ff3a2d6b6e413f590f8d784cd909a35efc547d8a95f7885dbdd93
Timestamp: 1721063737 Timestamp [UCT]: 2024-07-15 17:15:37 Age [y:d:h:m:s]: 00:335:00:35:19
Block: 1066386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239307 RingCT/type: yes/0
Extra: 01e7c5cf12f60ff3a2d6b6e413f590f8d784cd909a35efc547d8a95f7885dbdd9302110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c18066273c6d851775f1e1724eeb4c990d29769d5b97fc7dd86024a33360785 0.600000000000 1536959 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1066396, "vin": [ { "gen": { "height": 1066386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c18066273c6d851775f1e1724eeb4c990d29769d5b97fc7dd86024a33360785" } } ], "extra": [ 1, 231, 197, 207, 18, 246, 15, 243, 162, 214, 182, 228, 19, 245, 144, 248, 215, 132, 205, 144, 154, 53, 239, 197, 71, 216, 169, 95, 120, 133, 219, 221, 147, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8