Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 940361b85a990c57ecff3e527ebbb4d73ac45aae50db89b7a116acd05da0a4bb

Tx prefix hash: 9b4b6c7cdb12e656de9d2f06dd4aba1fa0af0956296dc5044109328752665422
Tx public key: 30459c1b3ec48fb7f8d4805390413ae8e1ca1237f7079bdddc4a1c96b1aea670
Timestamp: 1710633374 Timestamp [UCT]: 2024-03-16 23:56:14 Age [y:d:h:m:s]: 01:000:11:20:45
Block: 979920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261318 RingCT/type: yes/0
Extra: 0130459c1b3ec48fb7f8d4805390413ae8e1ca1237f7079bdddc4a1c96b1aea6700211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6750e8833fed2d24742a231115f7e71f0752c033b218010950efc1b0ea360165 0.600000000000 1439975 of 15

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": 979930, "vin": [ { "gen": { "height": 979920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6750e8833fed2d24742a231115f7e71f0752c033b218010950efc1b0ea360165" } } ], "extra": [ 1, 48, 69, 156, 27, 62, 196, 143, 183, 248, 212, 128, 83, 144, 65, 58, 232, 225, 202, 18, 55, 247, 7, 155, 221, 220, 74, 28, 150, 177, 174, 166, 112, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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