Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35324f48b0795f0b4e7920084bb761e42b570be14cf8ae9a3ae1b28bfc7d6c7d

Tx prefix hash: 29c4d35349695872f07006b2a506dbb7099a871b23cf460e774aa950b0a178a0
Tx public key: e160feea91ef3525653d7fe96977e7136aab28617a8b6ab6dc5f71f787df0a5b
Timestamp: 1608991274 Timestamp [UCT]: 2020-12-26 14:01:14 Age [y:d:h:m:s]: 03:334:14:23:25
Block: 169794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 991362 RingCT/type: yes/0
Extra: 01e160feea91ef3525653d7fe96977e7136aab28617a8b6ab6dc5f71f787df0a5b0211000003ee4ea414e5000000000000000000

1 output(s) for total of 168.036125511000 dcy

stealth address amount amount idx
00: 9f87d0377a0a3631f84a8f27bece1e860089c11d11c8cdb2ae859538a340584c 168.036125511000 317467 of 0

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": 169804, "vin": [ { "gen": { "height": 169794 } } ], "vout": [ { "amount": 168036125511, "target": { "key": "9f87d0377a0a3631f84a8f27bece1e860089c11d11c8cdb2ae859538a340584c" } } ], "extra": [ 1, 225, 96, 254, 234, 145, 239, 53, 37, 101, 61, 127, 233, 105, 119, 231, 19, 106, 171, 40, 97, 122, 139, 106, 182, 220, 95, 113, 247, 135, 223, 10, 91, 2, 17, 0, 0, 3, 238, 78, 164, 20, 229, 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