Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ce207879c9776c1736728c188b24de6ba5c6b57bef136f70153831b10242127

Tx prefix hash: e8a16f08df554e79776c121a37ae581ca9b8ff0e811cd913a8c648dc9cb6b918
Tx public key: 4df5ca8cb3fe1c6446b20dc49fec8d4d13ce069155b4e962fa71ed53e49019b7
Timestamp: 1709332316 Timestamp [UCT]: 2024-03-01 22:31:56 Age [y:d:h:m:s]: 01:251:11:32:17
Block: 969121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438459 RingCT/type: yes/0
Extra: 014df5ca8cb3fe1c6446b20dc49fec8d4d13ce069155b4e962fa71ed53e49019b70211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6f20f027dea766eee1887dde86d5f1e889d3e09532355930bd902f880b4c007 0.600000000000 1428948 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": 969131, "vin": [ { "gen": { "height": 969121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6f20f027dea766eee1887dde86d5f1e889d3e09532355930bd902f880b4c007" } } ], "extra": [ 1, 77, 245, 202, 140, 179, 254, 28, 100, 70, 178, 13, 196, 159, 236, 141, 77, 19, 206, 6, 145, 85, 180, 233, 98, 250, 113, 237, 83, 228, 144, 25, 183, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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