Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90bcc7e962d8ea25a398487530fb5505bbb999037e696c83844e4460fcfd20eb

Tx prefix hash: f057e5389acd40f4a129d3fad448e0c937df2b2e9356af4dc74b25bc827403c6
Tx public key: 035294057c1c1b995e41b137ef93bd3dfe9641fc6fe1ce1744ed582c5bd0a6d2
Timestamp: 1577742949 Timestamp [UCT]: 2019-12-30 21:55:49 Age [y:d:h:m:s]: 05:281:02:58:48
Block: 35347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1348312 RingCT/type: yes/0
Extra: 01035294057c1c1b995e41b137ef93bd3dfe9641fc6fe1ce1744ed582c5bd0a6d20211000000064ac5aa02000000000000000000

1 output(s) for total of 468.685556668000 dcy

stealth address amount amount idx
00: 934d7fd25245e32a88cc30b057014158fc3ab73506fac7843f5167cd0452ca7a 468.685556668000 59545 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": 35357, "vin": [ { "gen": { "height": 35347 } } ], "vout": [ { "amount": 468685556668, "target": { "key": "934d7fd25245e32a88cc30b057014158fc3ab73506fac7843f5167cd0452ca7a" } } ], "extra": [ 1, 3, 82, 148, 5, 124, 28, 27, 153, 94, 65, 177, 55, 239, 147, 189, 61, 254, 150, 65, 252, 111, 225, 206, 23, 68, 237, 88, 44, 91, 208, 166, 210, 2, 17, 0, 0, 0, 6, 74, 197, 170, 2, 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