Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9fb31906e0234f931c654505c119c194a9bdd9e0b3d92b2d1cae0cd4f947038

Tx prefix hash: ebfd64c66ccab0aaee971b35a9acad687680075e1e86d5d17236a8767b842a5a
Tx public key: 7869ca8472ea79f036b15148c17db51b3b479ae4696385ae3bd487f1da47db42
Timestamp: 1712193100 Timestamp [UCT]: 2024-04-04 01:11:40 Age [y:d:h:m:s]: 01:041:18:20:28
Block: 992807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290857 RingCT/type: yes/0
Extra: 017869ca8472ea79f036b15148c17db51b3b479ae4696385ae3bd487f1da47db4202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0c7ec64ce1fc77e0aefbce4ad3d120c31d6c1c880510964319ccdb48e85be19 0.600000000000 1453181 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": 992817, "vin": [ { "gen": { "height": 992807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0c7ec64ce1fc77e0aefbce4ad3d120c31d6c1c880510964319ccdb48e85be19" } } ], "extra": [ 1, 120, 105, 202, 132, 114, 234, 121, 240, 54, 177, 81, 72, 193, 125, 181, 27, 59, 71, 154, 228, 105, 99, 133, 174, 59, 212, 135, 241, 218, 71, 219, 66, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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