Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21e7229147761367fdb662f4d70c37a360badc68a10ff2c255f746e726e352f5

Tx prefix hash: 99891e79a9601ea8805eff7f1dd2350afb9a0284655812e8ea6f4727f9818a0f
Tx public key: 6aa9f1a5d335113bd5fb499e71a54d116918b5ab7569e33177df281090f0086c
Timestamp: 1734676454 Timestamp [UCT]: 2024-12-20 06:34:14 Age [y:d:h:m:s]: 00:172:15:49:19
Block: 1179145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123211 RingCT/type: yes/0
Extra: 016aa9f1a5d335113bd5fb499e71a54d116918b5ab7569e33177df281090f0086c021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4039521965d0079e9bcadd0acd6952a900fcdf5220a7e42b50759503c1ca0029 0.600000000000 1665536 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": 1179155, "vin": [ { "gen": { "height": 1179145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4039521965d0079e9bcadd0acd6952a900fcdf5220a7e42b50759503c1ca0029" } } ], "extra": [ 1, 106, 169, 241, 165, 211, 53, 17, 59, 213, 251, 73, 158, 113, 165, 77, 17, 105, 24, 181, 171, 117, 105, 227, 49, 119, 223, 40, 16, 144, 240, 8, 108, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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