Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab228d1219502b0b9a57a38505a0226bc284e5069515c3f6e9f049045428f0f8

Tx prefix hash: d76b34f63ac7428b8a865513aa83729404ff94b43dd28fd8cf0c771d29aa7437
Tx public key: 701a0b900c8e21b6ade4b1fa822998e962bc06f7917164d0f7194c10874b291a
Timestamp: 1709115768 Timestamp [UCT]: 2024-02-28 10:22:48 Age [y:d:h:m:s]: 01:315:10:57:22
Block: 967332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484264 RingCT/type: yes/0
Extra: 01701a0b900c8e21b6ade4b1fa822998e962bc06f7917164d0f7194c10874b291a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f96c2615a889cda802f63efac1577fee789c0d1679e3cf6dc99eab6ec975c65 0.600000000000 1427109 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": 967342, "vin": [ { "gen": { "height": 967332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f96c2615a889cda802f63efac1577fee789c0d1679e3cf6dc99eab6ec975c65" } } ], "extra": [ 1, 112, 26, 11, 144, 12, 142, 33, 182, 173, 228, 177, 250, 130, 41, 152, 233, 98, 188, 6, 247, 145, 113, 100, 208, 247, 25, 76, 16, 135, 75, 41, 26, 2, 17, 0, 0, 0, 1, 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