Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b4ee2e88fbde7a7a80dae96d8d9abfe572e45ebe6c6ee05884b12552e35808e

Tx prefix hash: 1db6d7d4b1e4623b964f802150dd346aa680800af5df3517e18af664b792be93
Tx public key: 9575dff1ddcafcdb6ebd404d195e46c7318466054bcdffcb54398e55058f1998
Timestamp: 1581101071 Timestamp [UCT]: 2020-02-07 18:44:31 Age [y:d:h:m:s]: 04:342:19:35:23
Block: 60759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1136468 RingCT/type: yes/0
Extra: 019575dff1ddcafcdb6ebd404d195e46c7318466054bcdffcb54398e55058f199802110000002c4ac5aa02000000000000000000

1 output(s) for total of 386.083310044000 dcy

stealth address amount amount idx
00: dad94fa811e87a5c037a544766cf096d8031f0dfd8aa831c5adccbb12e25ffb4 386.083310044000 111886 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": 60769, "vin": [ { "gen": { "height": 60759 } } ], "vout": [ { "amount": 386083310044, "target": { "key": "dad94fa811e87a5c037a544766cf096d8031f0dfd8aa831c5adccbb12e25ffb4" } } ], "extra": [ 1, 149, 117, 223, 241, 221, 202, 252, 219, 110, 189, 64, 77, 25, 94, 70, 199, 49, 132, 102, 5, 75, 205, 255, 203, 84, 57, 142, 85, 5, 143, 25, 152, 2, 17, 0, 0, 0, 44, 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