Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 225a7763a6f38c0c12803ee9b9944b68a1f844c6e757f2561ee87f6a37fee26e

Tx prefix hash: c2b4355209a288c190759c84084c5c7bdffc551c649a04957a8340194e15726f
Tx public key: 3c9085498c9327c5a5c5dbf4eb75966f7697fb49e81d164baae38be2538d731e
Timestamp: 1715909326 Timestamp [UCT]: 2024-05-17 01:28:46 Age [y:d:h:m:s]: 00:198:10:18:45
Block: 1023647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142034 RingCT/type: yes/0
Extra: 013c9085498c9327c5a5c5dbf4eb75966f7697fb49e81d164baae38be2538d731e02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e50dfca0952f16fa510dd406e60385c0c97fb5322e3d9fd3c654e6dbb94840dc 0.600000000000 1488778 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": 1023657, "vin": [ { "gen": { "height": 1023647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e50dfca0952f16fa510dd406e60385c0c97fb5322e3d9fd3c654e6dbb94840dc" } } ], "extra": [ 1, 60, 144, 133, 73, 140, 147, 39, 197, 165, 197, 219, 244, 235, 117, 150, 111, 118, 151, 251, 73, 232, 29, 22, 75, 170, 227, 139, 226, 83, 141, 115, 30, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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