Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f2bd0735340eb3f4e7219723b8a138b07ba3c3556f7f0a6cf9ae0b59e411bf1

Tx prefix hash: 4dc345dbd782568cf2bc16d339cff4a28bd08a4efd384153a203215f09e19cc0
Tx public key: 0349b248ae56b9a014b3f22d26f183cd05fe910d1d9ffddf0223cd84d3e4b705
Timestamp: 1755517450 Timestamp [UCT]: 2025-08-18 11:44:10 Age [y:d:h:m:s]: 00:088:06:42:09
Block: 1349163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62960 RingCT/type: yes/0
Extra: 010349b248ae56b9a014b3f22d26f183cd05fe910d1d9ffddf0223cd84d3e4b7050211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3416474d869eb6c12b8831c4a1df376f378b17bc3766419b7013b929db875673 0.600000000000 1837094 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": 1349173, "vin": [ { "gen": { "height": 1349163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3416474d869eb6c12b8831c4a1df376f378b17bc3766419b7013b929db875673" } } ], "extra": [ 1, 3, 73, 178, 72, 174, 86, 185, 160, 20, 179, 242, 45, 38, 241, 131, 205, 5, 254, 145, 13, 29, 159, 253, 223, 2, 35, 205, 132, 211, 228, 183, 5, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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