Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c3ab6fd0b0d4d0f43b8cf834d241f4c7f5a00ac8df6b5c72d523624996b0195

Tx prefix hash: a57b019411c2c9e8109b15439883e842c8ca9ba7b3cc49402a420c061b289116
Tx public key: adaa99acdc450905d8e7300e17218dcea72be90ae37ed4648ec823a3e09db4ab
Timestamp: 1717872175 Timestamp [UCT]: 2024-06-08 18:42:55 Age [y:d:h:m:s]: 00:227:23:21:35
Block: 1039921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163099 RingCT/type: yes/0
Extra: 01adaa99acdc450905d8e7300e17218dcea72be90ae37ed4648ec823a3e09db4ab0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e4035827614a36ceef62db201f1691c27e0be59d0c6df8e241cc9e26142a524 0.600000000000 1508576 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": 1039931, "vin": [ { "gen": { "height": 1039921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e4035827614a36ceef62db201f1691c27e0be59d0c6df8e241cc9e26142a524" } } ], "extra": [ 1, 173, 170, 153, 172, 220, 69, 9, 5, 216, 231, 48, 14, 23, 33, 141, 206, 167, 43, 233, 10, 227, 126, 212, 100, 142, 200, 35, 163, 224, 157, 180, 171, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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