Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 122fabd16dc09a57a178512e9e845cd2ac35e2d6dad4e5ea349c3467eedef6ad

Tx prefix hash: 84b3e274930b51ba03ffe64e2c314b0f76a1703bba273b4c18dfd4fd8ffe7373
Tx public key: e406924dd6e43381a6e457f8dc7e031a1668eb174e13837f6839c22ec8fb1124
Timestamp: 1763684659 Timestamp [UCT]: 2025-11-21 00:24:19 Age [y:d:h:m:s]: 00:036:11:00:00
Block: 1416582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26116 RingCT/type: yes/0
Extra: 01e406924dd6e43381a6e457f8dc7e031a1668eb174e13837f6839c22ec8fb112402110000000ed6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7aad500bd896d9acc15df9db1f5c3e6b5124d78bb9d36029cc57b57b78f201d3 0.600000000000 1905101 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": 1416592, "vin": [ { "gen": { "height": 1416582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7aad500bd896d9acc15df9db1f5c3e6b5124d78bb9d36029cc57b57b78f201d3" } } ], "extra": [ 1, 228, 6, 146, 77, 214, 228, 51, 129, 166, 228, 87, 248, 220, 126, 3, 26, 22, 104, 235, 23, 78, 19, 131, 127, 104, 57, 194, 46, 200, 251, 17, 36, 2, 17, 0, 0, 0, 14, 214, 225, 157, 124, 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