Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 377d09d5616966c6d4ace1a3cb3dab86d1f9fbf3d78f2b03073f77a14150b0de

Tx prefix hash: 38dd59819562ba879011b59e6f066dd1cf0a2b48ca68b7774fdab5e05d122994
Tx public key: 4c809f36c9a55d94eaf745e8b47a8adec90772fd59e64dca7b9c603664f57872
Timestamp: 1762467200 Timestamp [UCT]: 2025-11-06 22:13:20 Age [y:d:h:m:s]: 00:058:17:47:46
Block: 1406503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42078 RingCT/type: yes/0
Extra: 014c809f36c9a55d94eaf745e8b47a8adec90772fd59e64dca7b9c603664f57872021100000004df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b317df1b2fc9f458238faf552d92677652ac763fbd0620b8966c4aec8b4e98a1 0.600000000000 1894890 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": 1406513, "vin": [ { "gen": { "height": 1406503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b317df1b2fc9f458238faf552d92677652ac763fbd0620b8966c4aec8b4e98a1" } } ], "extra": [ 1, 76, 128, 159, 54, 201, 165, 93, 148, 234, 247, 69, 232, 180, 122, 138, 222, 201, 7, 114, 253, 89, 230, 77, 202, 123, 156, 96, 54, 100, 245, 120, 114, 2, 17, 0, 0, 0, 4, 223, 90, 36, 122, 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