Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4eb3e042487a83bccc9817ef3f8d3c95c1a07ac09526f77112288ed7bd9bde96

Tx prefix hash: fb3d2f9450f5855c6f0cf78510fa16d3321aa28c87c25a6a1216ec20c09782a7
Tx public key: 5c28b6113a895038fff4b1d32ac2278511d5b33536a2db19ded9798a772f3d04
Timestamp: 1740948453 Timestamp [UCT]: 2025-03-02 20:47:33 Age [y:d:h:m:s]: 00:256:10:57:32
Block: 1230768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181041 RingCT/type: yes/0
Extra: 015c28b6113a895038fff4b1d32ac2278511d5b33536a2db19ded9798a772f3d040211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a1a7b3af4a2fd2508fa252ad903325e6189f0df07ed13e0a8ee165b5d1d1135 0.600000000000 1717667 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": 1230778, "vin": [ { "gen": { "height": 1230768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a1a7b3af4a2fd2508fa252ad903325e6189f0df07ed13e0a8ee165b5d1d1135" } } ], "extra": [ 1, 92, 40, 182, 17, 58, 137, 80, 56, 255, 244, 177, 211, 42, 194, 39, 133, 17, 213, 179, 53, 54, 162, 219, 25, 222, 217, 121, 138, 119, 47, 61, 4, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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