Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5f3a2c5d367c88cccb30c0f755b272fdab62185c0b17638092c32130d87d0bc

Tx prefix hash: ffd47f1672231199fc9cabf578711ffe62e96e69faa10bd3448d2203b946174d
Tx public key: 9988e968bf0f3f767cbd9de302dc4802cbc1ba9f7896054cff6022d9c5e3eb60
Timestamp: 1577337697 Timestamp [UCT]: 2019-12-26 05:21:37 Age [y:d:h:m:s]: 04:340:16:15:47
Block: 31903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1132639 RingCT/type: yes/0
Extra: 019988e968bf0f3f767cbd9de302dc4802cbc1ba9f7896054cff6022d9c5e3eb6002110000005afeadaf7f000000000000000000

1 output(s) for total of 481.172134186000 dcy

stealth address amount amount idx
00: 7bdd084f26ee0f259b008d7c51de447e5bd1e89b640f277582408117161c53d3 481.172134186000 52925 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": 31913, "vin": [ { "gen": { "height": 31903 } } ], "vout": [ { "amount": 481172134186, "target": { "key": "7bdd084f26ee0f259b008d7c51de447e5bd1e89b640f277582408117161c53d3" } } ], "extra": [ 1, 153, 136, 233, 104, 191, 15, 63, 118, 124, 189, 157, 227, 2, 220, 72, 2, 203, 193, 186, 159, 120, 150, 5, 76, 255, 96, 34, 217, 197, 227, 235, 96, 2, 17, 0, 0, 0, 90, 254, 173, 175, 127, 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