Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 773ab08fb773c710de9b045b3bdcc2d2988bb77335449d2353280325355b2c64

Tx prefix hash: 94e62159adb67ac36cfa40a6e4e9a7dd9091092070260d94689627af223f15ff
Tx public key: d86122cccd4e597f97b0b700e4f1344818cbe4dc3baf12b5fc99b007e692cf87
Timestamp: 1636678448 Timestamp [UCT]: 2021-11-12 00:54:08 Age [y:d:h:m:s]: 03:052:20:05:12
Block: 372452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 816390 RingCT/type: yes/0
Extra: 01d86122cccd4e597f97b0b700e4f1344818cbe4dc3baf12b5fc99b007e692cf870211000000194a0f5013000000000000000000

1 output(s) for total of 35.802413366000 dcy

stealth address amount amount idx
00: 98966946ef2c8d10fd6a6b58026511a354f68b707edaa969796a70920166a29b 35.802413366000 754484 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": 372462, "vin": [ { "gen": { "height": 372452 } } ], "vout": [ { "amount": 35802413366, "target": { "key": "98966946ef2c8d10fd6a6b58026511a354f68b707edaa969796a70920166a29b" } } ], "extra": [ 1, 216, 97, 34, 204, 205, 78, 89, 127, 151, 176, 183, 0, 228, 241, 52, 72, 24, 203, 228, 220, 59, 175, 18, 181, 252, 153, 176, 7, 230, 146, 207, 135, 2, 17, 0, 0, 0, 25, 74, 15, 80, 19, 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