Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57ec9c0f33cd274c6efc27a36f9b7948a81b2403b9c6658e144836d62bbc27bb

Tx prefix hash: b820ae55d950a259d82326d518f96f5d88f41b64f8f2477f8b3cf9950af669ce
Tx public key: 31a755d9f7dff803812901f05d05f3b54511e4854047352cb1acdd04d776fc82
Timestamp: 1625646584 Timestamp [UCT]: 2021-07-07 08:29:44 Age [y:d:h:m:s]: 03:192:23:27:40
Block: 289595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 908151 RingCT/type: yes/0
Extra: 0131a755d9f7dff803812901f05d05f3b54511e4854047352cb1acdd04d776fc820211000000024b22f71d000000000000000000

1 output(s) for total of 67.367751775000 dcy

stealth address amount amount idx
00: a4e21994a66fbfd05eb2cfcd233174200ca5f9aa5ed6bce8795dffd64aa38165 67.367751775000 606561 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": 289605, "vin": [ { "gen": { "height": 289595 } } ], "vout": [ { "amount": 67367751775, "target": { "key": "a4e21994a66fbfd05eb2cfcd233174200ca5f9aa5ed6bce8795dffd64aa38165" } } ], "extra": [ 1, 49, 167, 85, 217, 247, 223, 248, 3, 129, 41, 1, 240, 93, 5, 243, 181, 69, 17, 228, 133, 64, 71, 53, 44, 177, 172, 221, 4, 215, 118, 252, 130, 2, 17, 0, 0, 0, 2, 75, 34, 247, 29, 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