Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 864f2453da8f427c14a7d26c1a13319ef616b2e5bddfde93d2f4f8b984ca1d44

Tx prefix hash: 7b964302566ea9276ca9aac4e0799ad84f26d0bb29497af11134f7e627f9a377
Tx public key: dbe4f24d5715e8a65f0fc92e886a932d9906528fc2bb06f9b152bac2d1b139ac
Timestamp: 1744844749 Timestamp [UCT]: 2025-04-16 23:05:49 Age [y:d:h:m:s]: 00:217:08:49:00
Block: 1263019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153081 RingCT/type: yes/0
Extra: 01dbe4f24d5715e8a65f0fc92e886a932d9906528fc2bb06f9b152bac2d1b139ac0211000000076c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 915f952cb4ca2f290016626abb86487a9e397d071769b66a53c1c56596a62862 0.600000000000 1750202 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": 1263029, "vin": [ { "gen": { "height": 1263019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "915f952cb4ca2f290016626abb86487a9e397d071769b66a53c1c56596a62862" } } ], "extra": [ 1, 219, 228, 242, 77, 87, 21, 232, 166, 95, 15, 201, 46, 136, 106, 147, 45, 153, 6, 82, 143, 194, 187, 6, 249, 177, 82, 186, 194, 209, 177, 57, 172, 2, 17, 0, 0, 0, 7, 108, 152, 170, 61, 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