Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ade0078438614e645cf2aed6e7ee672737d68b7ceb8a28d7d75e5c82adb89e78

Tx prefix hash: d4fedd4b0e329a8477ba6906b6cbf6e47edf79d66d37d5c97e77807f2c9ea1ab
Tx public key: 676f32c1fc1ac8b093e1c73c17c6c1af1826139f6a81716beec618fb6028cbca
Timestamp: 1578787051 Timestamp [UCT]: 2020-01-11 23:57:31 Age [y:d:h:m:s]: 04:323:22:23:50
Block: 43526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121034 RingCT/type: yes/0
Extra: 01676f32c1fc1ac8b093e1c73c17c6c1af1826139f6a81716beec618fb6028cbca0211000000088a2ee0d9000000000000000000

1 output(s) for total of 440.332900468000 dcy

stealth address amount amount idx
00: 02c6e693729a85bbc99e84f2f92f9f21fa8be1e18c033512b1754bb332747327 440.332900468000 78874 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": 43536, "vin": [ { "gen": { "height": 43526 } } ], "vout": [ { "amount": 440332900468, "target": { "key": "02c6e693729a85bbc99e84f2f92f9f21fa8be1e18c033512b1754bb332747327" } } ], "extra": [ 1, 103, 111, 50, 193, 252, 26, 200, 176, 147, 225, 199, 60, 23, 198, 193, 175, 24, 38, 19, 159, 106, 129, 113, 107, 238, 198, 24, 251, 96, 40, 203, 202, 2, 17, 0, 0, 0, 8, 138, 46, 224, 217, 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