Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3457040769e6d2bdb7bf83139c61b530a1cd23f1e1576345411dd68e03232427

Tx prefix hash: 02277b028fdc8b39000ff017b26f1f374f09ea140ec606a0d4e20280d5feb688
Tx public key: c605a2ba31dae15e0bf4c4d3045db2b4a78abfb86b97912b6a9f07dcd81d5573
Timestamp: 1712500982 Timestamp [UCT]: 2024-04-07 14:43:02 Age [y:d:h:m:s]: 01:215:14:54:30
Block: 995355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412805 RingCT/type: yes/0
Extra: 01c605a2ba31dae15e0bf4c4d3045db2b4a78abfb86b97912b6a9f07dcd81d55730211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dfa7e20245b92aa62add01f437051982d6f7adb1d29f83b74b241eeafa3c029 0.600000000000 1455763 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": 995365, "vin": [ { "gen": { "height": 995355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dfa7e20245b92aa62add01f437051982d6f7adb1d29f83b74b241eeafa3c029" } } ], "extra": [ 1, 198, 5, 162, 186, 49, 218, 225, 94, 11, 244, 196, 211, 4, 93, 178, 180, 167, 138, 191, 184, 107, 151, 145, 43, 106, 159, 7, 220, 216, 29, 85, 115, 2, 17, 0, 0, 0, 3, 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