Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba54ea4c492ca850d2ef1f5e219f97dd2058335a3dda6930867ba41d232697e1

Tx prefix hash: f60a2e27ecfa0e17d5a98fb14dd087a9fbbfaef081701030d4c158b9ee176c99
Tx public key: d529776ca9550a35576d3e390a20281e53fbf404fe3d3df2f818a42eeffbfd73
Timestamp: 1761309956 Timestamp [UCT]: 2025-10-24 12:45:56 Age [y:d:h:m:s]: 00:006:10:34:46
Block: 1396924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4619 RingCT/type: yes/0
Extra: 01d529776ca9550a35576d3e390a20281e53fbf404fe3d3df2f818a42eeffbfd7302110000000a5dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fc8d31a9c2af80a2a08b0e1f7bb1fba7dd43cbe4c0bee5ca3d98a6c308114df 0.600000000000 1885213 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": 1396934, "vin": [ { "gen": { "height": 1396924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fc8d31a9c2af80a2a08b0e1f7bb1fba7dd43cbe4c0bee5ca3d98a6c308114df" } } ], "extra": [ 1, 213, 41, 119, 108, 169, 85, 10, 53, 87, 109, 62, 57, 10, 32, 40, 30, 83, 251, 244, 4, 254, 61, 61, 242, 248, 24, 164, 46, 239, 251, 253, 115, 2, 17, 0, 0, 0, 10, 93, 251, 190, 42, 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