Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c863b08bf234fd7743ea850309cc0dae7247e30c7d168def62f27db58e3e65d9

Tx prefix hash: e140ccb9032c3d742d6db8cc54340dcb678022cf2b61397a8c9ca369a2c973b8
Tx public key: 8c95b21241ca10fc83f1ce151607a8a8813e86ebbf775b8c8857a9b79682a6b5
Timestamp: 1722157000 Timestamp [UCT]: 2024-07-28 08:56:40 Age [y:d:h:m:s]: 00:119:12:30:06
Block: 1075438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85512 RingCT/type: yes/0
Extra: 018c95b21241ca10fc83f1ce151607a8a8813e86ebbf775b8c8857a9b79682a6b5021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9661331f06f5b6bfe5ea33b47b897ec4ed8539f3250153d3722c2eda79b5f3f 0.600000000000 1547963 of 15

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": 1075448, "vin": [ { "gen": { "height": 1075438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9661331f06f5b6bfe5ea33b47b897ec4ed8539f3250153d3722c2eda79b5f3f" } } ], "extra": [ 1, 140, 149, 178, 18, 65, 202, 16, 252, 131, 241, 206, 21, 22, 7, 168, 168, 129, 62, 134, 235, 191, 119, 91, 140, 136, 87, 169, 183, 150, 130, 166, 181, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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