Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13434e8f42c7d8df782f7f6a5ca6bae8e85b50f07300f7ff5c13a7d87540b844

Tx prefix hash: b6812b24d09eebf8bb66d01b967446b4b15c3b5ac6ad4bd175f263d36f08c350
Tx public key: 24c0cd305af7180e017d65f3bcd0c64bbdd3e7cafe0c4c3fe5ebc824d02adaee
Timestamp: 1583346072 Timestamp [UCT]: 2020-03-04 18:21:12 Age [y:d:h:m:s]: 04:295:22:10:02
Block: 76294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1105989 RingCT/type: yes/0
Extra: 0124c0cd305af7180e017d65f3bcd0c64bbdd3e7cafe0c4c3fe5ebc824d02adaee021100000001c71d3ff9000000000000000000

1 output(s) for total of 342.931281375000 dcy

stealth address amount amount idx
00: 5fabd58c9e12072d0d35b18ddc2e933a8f6d652771b73c239f0e104916b61911 342.931281375000 140535 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": 76304, "vin": [ { "gen": { "height": 76294 } } ], "vout": [ { "amount": 342931281375, "target": { "key": "5fabd58c9e12072d0d35b18ddc2e933a8f6d652771b73c239f0e104916b61911" } } ], "extra": [ 1, 36, 192, 205, 48, 90, 247, 24, 14, 1, 125, 101, 243, 188, 208, 198, 75, 189, 211, 231, 202, 254, 12, 76, 63, 229, 235, 200, 36, 208, 42, 218, 238, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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