Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af64ced163e0e5178f483356f6a53968b00dfc4b35b3f7fa55f12ceb5bfd5f7f

Tx prefix hash: bda6d2439f373d768df49011c5ed164e971f4824bb3fb3eb628bf3ba590b9874
Tx public key: 06e21c25ebd6f14bb61bc25c82244fc5e8d3baae43080dbabe5068190f323930
Timestamp: 1716239416 Timestamp [UCT]: 2024-05-20 21:10:16 Age [y:d:h:m:s]: 01:004:15:04:52
Block: 1026384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264226 RingCT/type: yes/0
Extra: 0106e21c25ebd6f14bb61bc25c82244fc5e8d3baae43080dbabe5068190f32393002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 165f517b8a5abb9a62f6c5fcf2f61d09b7695d525d1ffb34b3b892ab7f42ca8e 0.600000000000 1493437 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": 1026394, "vin": [ { "gen": { "height": 1026384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "165f517b8a5abb9a62f6c5fcf2f61d09b7695d525d1ffb34b3b892ab7f42ca8e" } } ], "extra": [ 1, 6, 226, 28, 37, 235, 214, 241, 75, 182, 27, 194, 92, 130, 36, 79, 197, 232, 211, 186, 174, 67, 8, 13, 186, 190, 80, 104, 25, 15, 50, 57, 48, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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