Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 387a91b44451219fa13af14057763e0bf5345e86d3f7262b9ffebca9898b6916

Tx prefix hash: 36c56a035f6592abca6a7f1e03aca3bd4ed69256a6913f549bf710b7a7b51d30
Tx public key: 63723d71167ea6bb9e9c3ccea02323271a3c70030f238d60c87b8699b0b84a79
Timestamp: 1725932921 Timestamp [UCT]: 2024-09-10 01:48:41 Age [y:d:h:m:s]: 00:166:06:20:09
Block: 1106746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118616 RingCT/type: yes/0
Extra: 0163723d71167ea6bb9e9c3ccea02323271a3c70030f238d60c87b8699b0b84a7902110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2171a1967910fe7aece0ae95b337dace9ef9f0d054c2e624d1d5a93008434691 0.600000000000 1584347 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": 1106756, "vin": [ { "gen": { "height": 1106746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2171a1967910fe7aece0ae95b337dace9ef9f0d054c2e624d1d5a93008434691" } } ], "extra": [ 1, 99, 114, 61, 113, 22, 126, 166, 187, 158, 156, 60, 206, 160, 35, 35, 39, 26, 60, 112, 3, 15, 35, 141, 96, 200, 123, 134, 153, 176, 184, 74, 121, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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