Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70446e6321ccc0a2a313f0d4d7d4402977756ef498e40c16f81494d4853b6ed8

Tx prefix hash: ffe436c233d81ae1ad32b9c3de1e425a085176412803eb5c436e1143f91c32c8
Tx public key: cf84906f3dff9700e6cf4f28f33d74118a6e4fd78c4dbee1f792b65664f06d05
Timestamp: 1726287841 Timestamp [UCT]: 2024-09-14 04:24:01 Age [y:d:h:m:s]: 00:117:10:15:44
Block: 1109678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83981 RingCT/type: yes/0
Extra: 01cf84906f3dff9700e6cf4f28f33d74118a6e4fd78c4dbee1f792b65664f06d05021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8984064e5f79bf562f693a13738b1098a989aba872bb449c38429f35f2a3e533 0.600000000000 1588021 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": 1109688, "vin": [ { "gen": { "height": 1109678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8984064e5f79bf562f693a13738b1098a989aba872bb449c38429f35f2a3e533" } } ], "extra": [ 1, 207, 132, 144, 111, 61, 255, 151, 0, 230, 207, 79, 40, 243, 61, 116, 17, 138, 110, 79, 215, 140, 77, 190, 225, 247, 146, 182, 86, 100, 240, 109, 5, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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