Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eab40f1405cc1371374a4f885feb8bd45b6eef4004b6ab8a51f5cd16838866b8

Tx prefix hash: 128b7a5be7c205a50c6719b21e5ae9cc915cd7a7e691ccd8e972690242787267
Tx public key: 905cb6c8050f29640e672ecf8e31b86fe3cbdd4877e60e7ecf83d92866581420
Timestamp: 1580263130 Timestamp [UCT]: 2020-01-29 01:58:50 Age [y:d:h:m:s]: 04:303:20:10:06
Block: 54267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1108133 RingCT/type: yes/0
Extra: 01905cb6c8050f29640e672ecf8e31b86fe3cbdd4877e60e7ecf83d92866581420021100000001dcee4b4d000000000000000000

1 output(s) for total of 405.712065236000 dcy

stealth address amount amount idx
00: 7e77fc52ebc23c35a8d44c8aaf6596424b3716ea85f488ff655d6171668412ef 405.712065236000 100599 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": 54277, "vin": [ { "gen": { "height": 54267 } } ], "vout": [ { "amount": 405712065236, "target": { "key": "7e77fc52ebc23c35a8d44c8aaf6596424b3716ea85f488ff655d6171668412ef" } } ], "extra": [ 1, 144, 92, 182, 200, 5, 15, 41, 100, 14, 103, 46, 207, 142, 49, 184, 111, 227, 203, 221, 72, 119, 230, 14, 126, 207, 131, 217, 40, 102, 88, 20, 32, 2, 17, 0, 0, 0, 1, 220, 238, 75, 77, 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