Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dcfd02db29b3695cbc139b17b4f76960b44dc8283ca38fb886390a358b83cdf

Tx prefix hash: 11e5f0c115cb8c23abdf03e6bcdbf38368fd0cfaafc73794c61bc6cc2f04e719
Tx public key: 408a2accd3a2e8d6f64ad18ff98b33bc00256ef18d7c802886dbb0576af74d7f
Timestamp: 1750940282 Timestamp [UCT]: 2025-06-26 12:18:02 Age [y:d:h:m:s]: 00:180:13:38:04
Block: 1313173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127086 RingCT/type: yes/0
Extra: 01408a2accd3a2e8d6f64ad18ff98b33bc00256ef18d7c802886dbb0576af74d7f021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b69c7d307810c57afcecd13483d3f370f59eb73889e6061ea5e2d21bf34e6b5 0.600000000000 1800812 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": 1313183, "vin": [ { "gen": { "height": 1313173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b69c7d307810c57afcecd13483d3f370f59eb73889e6061ea5e2d21bf34e6b5" } } ], "extra": [ 1, 64, 138, 42, 204, 211, 162, 232, 214, 246, 74, 209, 143, 249, 139, 51, 188, 0, 37, 110, 241, 141, 124, 128, 40, 134, 219, 176, 87, 106, 247, 77, 127, 2, 17, 0, 0, 0, 2, 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