Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8476c013919b93f4ab6ba576159f174a85ef9730135cf7e4e51154822eb8def

Tx prefix hash: 004fdbcb45989d244e7dbd4524feb5645ad57d2679550a54e88129a68fecc80e
Tx public key: 01a987712f5a2ec9aa2b2e8677c9498faaa34caeebc0b0d1fe4f1175e829a07c
Timestamp: 1719518926 Timestamp [UCT]: 2024-06-27 20:08:46 Age [y:d:h:m:s]: 00:196:08:40:32
Block: 1053562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140518 RingCT/type: yes/0
Extra: 0101a987712f5a2ec9aa2b2e8677c9498faaa34caeebc0b0d1fe4f1175e829a07c0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fd4ed2b8131ec2ccaca56bc197d8a44ee43e24c681472e138f0be2e3edb08b6 0.600000000000 1523909 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": 1053572, "vin": [ { "gen": { "height": 1053562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fd4ed2b8131ec2ccaca56bc197d8a44ee43e24c681472e138f0be2e3edb08b6" } } ], "extra": [ 1, 1, 169, 135, 113, 47, 90, 46, 201, 170, 43, 46, 134, 119, 201, 73, 143, 170, 163, 76, 174, 235, 192, 176, 209, 254, 79, 17, 117, 232, 41, 160, 124, 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