Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 262c45c1dc016095ffba66f5528d86cb33f5ec620645e1ed1f0cf373b45fcac3

Tx prefix hash: 6665dfdece1ca8e48ca37145e1e24922642bbaeb52878c16ca2f4c513d037a08
Tx public key: 8139e891ec5c13724d16d470d77c15e2b6a3b4a9dbd504c416ac0407fa80844e
Timestamp: 1747636514 Timestamp [UCT]: 2025-05-19 06:35:14 Age [y:d:h:m:s]: 00:216:23:11:00
Block: 1286131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152816 RingCT/type: yes/0
Extra: 018139e891ec5c13724d16d470d77c15e2b6a3b4a9dbd504c416ac0407fa80844e0211000000079f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2c19c8ffc81a79e6ef042a9e8e8f509bddc1c6c3e0929bf1a36422168c8b111 0.600000000000 1773596 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": 1286141, "vin": [ { "gen": { "height": 1286131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2c19c8ffc81a79e6ef042a9e8e8f509bddc1c6c3e0929bf1a36422168c8b111" } } ], "extra": [ 1, 129, 57, 232, 145, 236, 92, 19, 114, 77, 22, 212, 112, 215, 124, 21, 226, 182, 163, 180, 169, 219, 213, 4, 196, 22, 172, 4, 7, 250, 128, 132, 78, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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