Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7f4d0b6fd1e671cc8da640c21b5a6fef275141769aefbb13c6cf4d5c5aa0b2a

Tx prefix hash: a4005a1556dc21a779688ea42d4e7ccfbd8e2e02d6581c8f4d0c7d5d0e2b2d91
Tx public key: ef7842cb3413a9b0872baae94f0b8fd6863aa860016731ed6e63acb112e9fbd8
Timestamp: 1705508289 Timestamp [UCT]: 2024-01-17 16:18:09 Age [y:d:h:m:s]: 01:122:05:12:00
Block: 937398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348463 RingCT/type: yes/0
Extra: 01ef7842cb3413a9b0872baae94f0b8fd6863aa860016731ed6e63acb112e9fbd802110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 538043be37fa808cf2fd816a576f9fecd64cd65e432871807bf6e85c02761729 0.600000000000 1395452 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": 937408, "vin": [ { "gen": { "height": 937398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "538043be37fa808cf2fd816a576f9fecd64cd65e432871807bf6e85c02761729" } } ], "extra": [ 1, 239, 120, 66, 203, 52, 19, 169, 176, 135, 43, 170, 233, 79, 11, 143, 214, 134, 58, 168, 96, 1, 103, 49, 237, 110, 99, 172, 177, 18, 233, 251, 216, 2, 17, 0, 0, 0, 8, 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