Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a909f8696c7d976bbc06442d57115cd4abb853d6b2225cd572694b38f4555829

Tx prefix hash: 486046cfa1fb14ba3c305b3cd2abb72594201e080bcd834b9a3ff9c550995551
Tx public key: 1df960033c4c26ce8a4f3e211551d8cf2f62fbb41f3e58107e1876a107818899
Timestamp: 1587144763 Timestamp [UCT]: 2020-04-17 17:32:43 Age [y:d:h:m:s]: 04:227:17:04:08
Block: 93793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1071130 RingCT/type: yes/0
Extra: 011df960033c4c26ce8a4f3e211551d8cf2f62fbb41f3e58107e1876a107818899021100000143209b4bc8000000000000000000

1 output(s) for total of 300.072105551000 dcy

stealth address amount amount idx
00: acf7c58fc75572d69b92fd045dc2e6d222308ed46c6856ed6f1aeaba677101f0 300.072105551000 166895 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": 93803, "vin": [ { "gen": { "height": 93793 } } ], "vout": [ { "amount": 300072105551, "target": { "key": "acf7c58fc75572d69b92fd045dc2e6d222308ed46c6856ed6f1aeaba677101f0" } } ], "extra": [ 1, 29, 249, 96, 3, 60, 76, 38, 206, 138, 79, 62, 33, 21, 81, 216, 207, 47, 98, 251, 180, 31, 62, 88, 16, 126, 24, 118, 161, 7, 129, 136, 153, 2, 17, 0, 0, 1, 67, 32, 155, 75, 200, 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