Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb9b68cb8caa04ab3ead1da385c93f4e2731d78caac29b0ac01a7a0108f8cfab

Tx prefix hash: dce3af4e2ac18fa111ef7c0a2760c97e388c566dc4df2ef92ef5f9b9bfad71ae
Tx public key: 82939f25df5a31cd9a7fc84896ca9bf34ff1a697001e596be9584f01231924e8
Timestamp: 1603102440 Timestamp [UCT]: 2020-10-19 10:14:00 Age [y:d:h:m:s]: 05:013:04:59:43
Block: 141918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1260091 RingCT/type: yes/0
Extra: 0182939f25df5a31cd9a7fc84896ca9bf34ff1a697001e596be9584f01231924e802110000000b3a3a2186000000000000000000

1 output(s) for total of 207.858340473000 dcy

stealth address amount amount idx
00: db607e5662a10e0321be100b2364ae83da1dc2081797798f202137e056c476a6 207.858340473000 235866 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": 141928, "vin": [ { "gen": { "height": 141918 } } ], "vout": [ { "amount": 207858340473, "target": { "key": "db607e5662a10e0321be100b2364ae83da1dc2081797798f202137e056c476a6" } } ], "extra": [ 1, 130, 147, 159, 37, 223, 90, 49, 205, 154, 127, 200, 72, 150, 202, 155, 243, 79, 241, 166, 151, 0, 30, 89, 107, 233, 88, 79, 1, 35, 25, 36, 232, 2, 17, 0, 0, 0, 11, 58, 58, 33, 134, 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