Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43cbf6eab1f391b7bd682cade6a1bef72a531152e650759abb2bdae89c0c2044

Tx prefix hash: 578604a45bd4e296640a3e922fa61071d70c38bfc230b3415b9bbe5adab6890b
Tx public key: b8ace2f17e6e8da41f6f691793d2e340b87e952a9cfa0aeda1405f9187848e30
Timestamp: 1712257795 Timestamp [UCT]: 2024-04-04 19:09:55 Age [y:d:h:m:s]: 01:241:07:41:50
Block: 993355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431189 RingCT/type: yes/0
Extra: 01b8ace2f17e6e8da41f6f691793d2e340b87e952a9cfa0aeda1405f9187848e300211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89bc2217f28e6b402be7b762a5fe354abfcdf077749910d6e90d9f33ed747041 0.600000000000 1453741 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": 993365, "vin": [ { "gen": { "height": 993355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89bc2217f28e6b402be7b762a5fe354abfcdf077749910d6e90d9f33ed747041" } } ], "extra": [ 1, 184, 172, 226, 241, 126, 110, 141, 164, 31, 111, 105, 23, 147, 210, 227, 64, 184, 126, 149, 42, 156, 250, 10, 237, 161, 64, 95, 145, 135, 132, 142, 48, 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