Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 722cc15d5b98bca00e6890eb1ec8afb7bea472cf2edb208a64d7b5b01ee6257f

Tx prefix hash: dfed8bcc77f6dcff255c4af414000f882c81b9f6f5a8f64aeaf5dbdce1daee90
Tx public key: 5ef78300c0e49e21db2d6c9c0f4eb023e63ef03374a5b5d5b770458e10d2a683
Timestamp: 1722502727 Timestamp [UCT]: 2024-08-01 08:58:47 Age [y:d:h:m:s]: 00:284:18:11:47
Block: 1078308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203435 RingCT/type: yes/0
Extra: 015ef78300c0e49e21db2d6c9c0f4eb023e63ef03374a5b5d5b770458e10d2a68302110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d7e4bfaffd9c0a625f8cc51241fb0571360e2fa73b93c2a7167ef5cdd8d8a49 0.600000000000 1550885 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": 1078318, "vin": [ { "gen": { "height": 1078308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d7e4bfaffd9c0a625f8cc51241fb0571360e2fa73b93c2a7167ef5cdd8d8a49" } } ], "extra": [ 1, 94, 247, 131, 0, 192, 228, 158, 33, 219, 45, 108, 156, 15, 78, 176, 35, 230, 62, 240, 51, 116, 165, 181, 213, 183, 112, 69, 142, 16, 210, 166, 131, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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