Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd0d35c5b434136f45543dac813d604274aa3c5e6879b8118170ad1f9953dce6

Tx prefix hash: 3123e7ebd29da9eea7ec75c715f654cf73c769e009621684aa24354128d957ca
Tx public key: 4eea1ea0fd86de70014d8ba3836224bc30f4e8ebfa531293ce29f0cd8752e203
Timestamp: 1709678355 Timestamp [UCT]: 2024-03-05 22:39:15 Age [y:d:h:m:s]: 01:104:03:37:02
Block: 971990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335365 RingCT/type: yes/0
Extra: 014eea1ea0fd86de70014d8ba3836224bc30f4e8ebfa531293ce29f0cd8752e20302110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94c84b0ae3f2edaa56acfcfbe43d9b13bb8f3b59a3e6d77b8a029b60f5c23e47 0.600000000000 1431895 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": 972000, "vin": [ { "gen": { "height": 971990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94c84b0ae3f2edaa56acfcfbe43d9b13bb8f3b59a3e6d77b8a029b60f5c23e47" } } ], "extra": [ 1, 78, 234, 30, 160, 253, 134, 222, 112, 1, 77, 139, 163, 131, 98, 36, 188, 48, 244, 232, 235, 250, 83, 18, 147, 206, 41, 240, 205, 135, 82, 226, 3, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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