Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 667e13ae45088df8b1a200530fe1d69d777148287cfa6e982108bc8852e3b366

Tx prefix hash: c6ffb254006ca2711a89ebda6a518d5bb2f47fac47bbd7ce828f3d56a5095b61
Tx public key: aea289f692d282ae66f5c2b695609366d4c1d23fc2d107ec633f2d3c2532b221
Timestamp: 1701284346 Timestamp [UCT]: 2023-11-29 18:59:06 Age [y:d:h:m:s]: 01:115:22:58:58
Block: 902383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344031 RingCT/type: yes/0
Extra: 01aea289f692d282ae66f5c2b695609366d4c1d23fc2d107ec633f2d3c2532b221021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.628102474000 dcy

stealth address amount amount idx
00: cabd65bcfcdf04cd72b4f4325e26142d548de2090576f104e077963944fde270 0.628102474000 1359022 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": 902393, "vin": [ { "gen": { "height": 902383 } } ], "vout": [ { "amount": 628102474, "target": { "key": "cabd65bcfcdf04cd72b4f4325e26142d548de2090576f104e077963944fde270" } } ], "extra": [ 1, 174, 162, 137, 246, 146, 210, 130, 174, 102, 245, 194, 182, 149, 96, 147, 102, 212, 193, 210, 63, 194, 209, 7, 236, 99, 63, 45, 60, 37, 50, 178, 33, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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