Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d58bb675b0238550cb0b70c15cee8e079dc6dc105fa7fbf7ed64a63ac51dbdf7

Tx prefix hash: 9a3d1d2d7ae1625c338ad42df59bbd515fd77f881141b98b4b87d62552ac78e0
Tx public key: 640dfc72002bbdf84ef7970e90a4d933d997fce113b6e7c1d0ea556bd975cf8a
Timestamp: 1743474784 Timestamp [UCT]: 2025-04-01 02:33:04 Age [y:d:h:m:s]: 00:233:04:19:35
Block: 1251675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164391 RingCT/type: yes/0
Extra: 01640dfc72002bbdf84ef7970e90a4d933d997fce113b6e7c1d0ea556bd975cf8a021100000005a2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b846b919f05fb60dd84105422cf00591f3366a24e69ba1887b9ff1612c9902fa 0.600000000000 1738744 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": 1251685, "vin": [ { "gen": { "height": 1251675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b846b919f05fb60dd84105422cf00591f3366a24e69ba1887b9ff1612c9902fa" } } ], "extra": [ 1, 100, 13, 252, 114, 0, 43, 189, 248, 78, 247, 151, 14, 144, 164, 217, 51, 217, 151, 252, 225, 19, 182, 231, 193, 208, 234, 85, 107, 217, 117, 207, 138, 2, 17, 0, 0, 0, 5, 162, 237, 1, 107, 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