Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1825820362f124f6d9a7810c03a616e42aa4e03dc1a3507fbd0d92920d75c1fc

Tx prefix hash: ec3c45703e25f5a0ea74ab4053f878dd7072db1ca25b0b2dcb2b8c76fbc98466
Tx public key: 0b49a92cae3684f8a29963355ecdc41c94700a77535f1b95f3ff9d8a5e6d5834
Timestamp: 1763788055 Timestamp [UCT]: 2025-11-22 05:07:35 Age [y:d:h:m:s]: 00:006:02:06:07
Block: 1417443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4368 RingCT/type: yes/0
Extra: 010b49a92cae3684f8a29963355ecdc41c94700a77535f1b95f3ff9d8a5e6d583402110000000270609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31a41ebc13f74a81145758196aef16043a507e5ca6b2fc86fa0e565527e6bed3 0.600000000000 1905966 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": 1417453, "vin": [ { "gen": { "height": 1417443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31a41ebc13f74a81145758196aef16043a507e5ca6b2fc86fa0e565527e6bed3" } } ], "extra": [ 1, 11, 73, 169, 44, 174, 54, 132, 248, 162, 153, 99, 53, 94, 205, 196, 28, 148, 112, 10, 119, 83, 95, 27, 149, 243, 255, 157, 138, 94, 109, 88, 52, 2, 17, 0, 0, 0, 2, 112, 96, 157, 3, 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