Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fab328b9838c30e1118e1f37095594cbfee3513b86b0c26ae968fea8da4258fd

Tx prefix hash: b8d63b4867ea88be0e47589dc0bf8cf12129ef02be757959247eb8b1ac1cf299
Tx public key: b69646ad929f57e8ef7ee4018133795d2486f84fd86c9c40baf4d54728c018dc
Timestamp: 1717974096 Timestamp [UCT]: 2024-06-09 23:01:36 Age [y:d:h:m:s]: 00:341:03:32:39
Block: 1040760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243827 RingCT/type: yes/0
Extra: 01b69646ad929f57e8ef7ee4018133795d2486f84fd86c9c40baf4d54728c018dc02110000000e7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e8a773665d4bce160293490c6018f2c04dc50487b98ba3e3abd62ef594d4989 0.600000000000 1509421 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": 1040770, "vin": [ { "gen": { "height": 1040760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e8a773665d4bce160293490c6018f2c04dc50487b98ba3e3abd62ef594d4989" } } ], "extra": [ 1, 182, 150, 70, 173, 146, 159, 87, 232, 239, 126, 228, 1, 129, 51, 121, 93, 36, 134, 248, 79, 216, 108, 156, 64, 186, 244, 213, 71, 40, 192, 24, 220, 2, 17, 0, 0, 0, 14, 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