Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68d21b215b7cda58df0f6fea99d254800870362dde6dee3ddcf40dab574cebff

Tx prefix hash: 8807cb1d627b0f8ec5397bed7faf8b43a93c83f0528602a12e89acb297888d22
Tx public key: 9966a299d2a4a01af8cd3ee380a0862bca4ed29197e874920a177f8bbbee3cf8
Timestamp: 1738384105 Timestamp [UCT]: 2025-02-01 04:28:25 Age [y:d:h:m:s]: 00:293:05:07:25
Block: 1209539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207317 RingCT/type: yes/0
Extra: 019966a299d2a4a01af8cd3ee380a0862bca4ed29197e874920a177f8bbbee3cf8021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cf23c2975f4b45c88f7219f162fe36ffd9bd237b2682acdb94d66bd25544f2a 0.600000000000 1696284 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": 1209549, "vin": [ { "gen": { "height": 1209539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cf23c2975f4b45c88f7219f162fe36ffd9bd237b2682acdb94d66bd25544f2a" } } ], "extra": [ 1, 153, 102, 162, 153, 210, 164, 160, 26, 248, 205, 62, 227, 128, 160, 134, 43, 202, 78, 210, 145, 151, 232, 116, 146, 10, 23, 127, 139, 187, 238, 60, 248, 2, 17, 0, 0, 0, 3, 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