Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8c0f73645a46cf1f1adb5695dd75d99f31dfc4594fb5e49145ea08f877bcab9

Tx prefix hash: 020dde3f389aa023d2d2a4ddcf25506518484740b486fce6bb116e6aaf4a8a63
Tx public key: 5f413509e75fb649b1dbc340709ae5702a2dad146081c4a5636de136a2c5cb7d
Timestamp: 1582097108 Timestamp [UCT]: 2020-02-19 07:25:08 Age [y:d:h:m:s]: 05:020:08:47:54
Block: 67862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1167785 RingCT/type: yes/0
Extra: 015f413509e75fb649b1dbc340709ae5702a2dad146081c4a5636de136a2c5cb7d02110000000356c366d3000000000000000000

1 output(s) for total of 365.717573796000 dcy

stealth address amount amount idx
00: 2b1239e4829aeccfbb5dbbfaf6a47c44c007b7733fc29066ed43e7428830755c 365.717573796000 125054 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": 67872, "vin": [ { "gen": { "height": 67862 } } ], "vout": [ { "amount": 365717573796, "target": { "key": "2b1239e4829aeccfbb5dbbfaf6a47c44c007b7733fc29066ed43e7428830755c" } } ], "extra": [ 1, 95, 65, 53, 9, 231, 95, 182, 73, 177, 219, 195, 64, 112, 154, 229, 112, 42, 45, 173, 20, 96, 129, 196, 165, 99, 109, 225, 54, 162, 197, 203, 125, 2, 17, 0, 0, 0, 3, 86, 195, 102, 211, 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