Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d324cf1541ba5eca8928b793001d4b88738b5efae19d963135ac8daf4c21de7

Tx prefix hash: 606b887471af14ad42f9485f17f07c0dca2a5e29480983ce6c50d6ed46a0c64e
Tx public key: 5145d1c9b12da3af5beff47681e59ea4a4a516affb9bf35ce468bfe9fc1717b5
Timestamp: 1759569083 Timestamp [UCT]: 2025-10-04 09:11:23 Age [y:d:h:m:s]: 00:003:13:36:26
Block: 1382482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2547 RingCT/type: yes/0
Extra: 015145d1c9b12da3af5beff47681e59ea4a4a516affb9bf35ce468bfe9fc1717b5021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56c9e7b768293f5b6c4d9a0fc0c3427cd214c109ef197ce8bceff323379a2920 0.600000000000 1870617 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": 1382492, "vin": [ { "gen": { "height": 1382482 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56c9e7b768293f5b6c4d9a0fc0c3427cd214c109ef197ce8bceff323379a2920" } } ], "extra": [ 1, 81, 69, 209, 201, 177, 45, 163, 175, 91, 239, 244, 118, 129, 229, 158, 164, 164, 165, 22, 175, 251, 155, 243, 92, 228, 104, 191, 233, 252, 23, 23, 181, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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