Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e0c52a3c3034ab2884c102423af7249fe776a4643736d131122f1478187c354

Tx prefix hash: 0cd0e89f1db5999ed4d24053b58d7d4c988f5a78b86e8736b24a21a79e6abb0f
Tx public key: a4d46a39d3c1ada70856a4b0a6770dc75ff50cd0c3aeb3f9cb34f4aa2492801e
Timestamp: 1632289105 Timestamp [UCT]: 2021-09-22 05:38:25 Age [y:d:h:m:s]: 03:101:18:59:36
Block: 338598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 848910 RingCT/type: yes/0
Extra: 01a4d46a39d3c1ada70856a4b0a6770dc75ff50cd0c3aeb3f9cb34f4aa2492801e02110000000bfdc024ec000000000000000000

1 output(s) for total of 46.353731570000 dcy

stealth address amount amount idx
00: 87c240a60dbd3272062e96f583d9d48b59bdf07f022273d591e6f6a12d0577c3 46.353731570000 696789 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": 338608, "vin": [ { "gen": { "height": 338598 } } ], "vout": [ { "amount": 46353731570, "target": { "key": "87c240a60dbd3272062e96f583d9d48b59bdf07f022273d591e6f6a12d0577c3" } } ], "extra": [ 1, 164, 212, 106, 57, 211, 193, 173, 167, 8, 86, 164, 176, 166, 119, 13, 199, 95, 245, 12, 208, 195, 174, 179, 249, 203, 52, 244, 170, 36, 146, 128, 30, 2, 17, 0, 0, 0, 11, 253, 192, 36, 236, 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