Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0dc1e80e63cf1a2bf55b397f0e19cebc56c6ae8be9623e9f8d29da367c8cc1d

Tx prefix hash: d097fc868a80f80483e03845f6b8e2ff36569bb25b8427a403d7f464c1595ca5
Tx public key: 9d65d28cc0edcc11b973180670e84a5e55b509aba5e727d4ef4ac4c763749de5
Timestamp: 1731756034 Timestamp [UCT]: 2024-11-16 11:20:34 Age [y:d:h:m:s]: 00:180:14:42:54
Block: 1154935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128913 RingCT/type: yes/0
Extra: 019d65d28cc0edcc11b973180670e84a5e55b509aba5e727d4ef4ac4c763749de50211000000101f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d270e17fdc81199fcfa2cadeee706d5b5b1ba96731cc0f0889389b8adb274869 0.600000000000 1640548 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": 1154945, "vin": [ { "gen": { "height": 1154935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d270e17fdc81199fcfa2cadeee706d5b5b1ba96731cc0f0889389b8adb274869" } } ], "extra": [ 1, 157, 101, 210, 140, 192, 237, 204, 17, 185, 115, 24, 6, 112, 232, 74, 94, 85, 181, 9, 171, 165, 231, 39, 212, 239, 74, 196, 199, 99, 116, 157, 229, 2, 17, 0, 0, 0, 16, 31, 10, 83, 235, 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