Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 960212d410c1d78dd01b2f14482f31fef9a5dcdb537e0136ca23ecdea0d0b747

Tx prefix hash: 3a373885a4568f332501e801b5327fcaab8cd6285ccf063af62b66c9bf9d4aee
Tx public key: 1f99c83cfca50bf9dc3e9d8ed0be5ecfddc14ba8377b9ef7bd8fa028feb8715f
Timestamp: 1709594477 Timestamp [UCT]: 2024-03-04 23:21:17 Age [y:d:h:m:s]: 00:357:06:16:57
Block: 971295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255428 RingCT/type: yes/0
Extra: 011f99c83cfca50bf9dc3e9d8ed0be5ecfddc14ba8377b9ef7bd8fa028feb8715f0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 474c3ded7515212d496b28433570cc107a924eec988c9ad007684d611185caa1 0.600000000000 1431182 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": 971305, "vin": [ { "gen": { "height": 971295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "474c3ded7515212d496b28433570cc107a924eec988c9ad007684d611185caa1" } } ], "extra": [ 1, 31, 153, 200, 60, 252, 165, 11, 249, 220, 62, 157, 142, 208, 190, 94, 207, 221, 193, 75, 168, 55, 123, 158, 247, 189, 143, 160, 40, 254, 184, 113, 95, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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