Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8f1490bcd7fd60fb95e89cafa089e5ab752a56060eba53986a6d43f34847a37

Tx prefix hash: 5ed3de948e5d6ad309b0ad8edd6580d14596c92cf928daa527b1aed899b6805b
Tx public key: e09439a07fe3f85b53e3d9ac5c59f64044c61c80ff84745af66d7dc9fa6ca13b
Timestamp: 1727866454 Timestamp [UCT]: 2024-10-02 10:54:14 Age [y:d:h:m:s]: 00:181:04:44:45
Block: 1122781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129284 RingCT/type: yes/0
Extra: 01e09439a07fe3f85b53e3d9ac5c59f64044c61c80ff84745af66d7dc9fa6ca13b02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4836dc1b6101ada72b4a20ce06118830ba6bd3625e3eed5e83032dc660f4bcf1 0.600000000000 1605304 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": 1122791, "vin": [ { "gen": { "height": 1122781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4836dc1b6101ada72b4a20ce06118830ba6bd3625e3eed5e83032dc660f4bcf1" } } ], "extra": [ 1, 224, 148, 57, 160, 127, 227, 248, 91, 83, 227, 217, 172, 92, 89, 246, 64, 68, 198, 28, 128, 255, 132, 116, 90, 246, 109, 125, 201, 250, 108, 161, 59, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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