Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a02f1569f284d8c4fabb0d3d550f05b34147c2556b4a29da41edb5e0aa3096a

Tx prefix hash: 25ce4e4ef666910665d30073eeb44519e78f81c0ca65d02078a591598bdfffbb
Tx public key: ebb30be0203cc21917a9e4fb67cecf2139d908e12172f7a2d4aaa5f654dc6ebf
Timestamp: 1708269146 Timestamp [UCT]: 2024-02-18 15:12:26 Age [y:d:h:m:s]: 00:353:04:41:51
Block: 960300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252550 RingCT/type: yes/0
Extra: 01ebb30be0203cc21917a9e4fb67cecf2139d908e12172f7a2d4aaa5f654dc6ebf0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad260a947db43e69addfcc25055d2d57f0e0def98475fdaa7f600fb58abdd35b 0.600000000000 1419863 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": 960310, "vin": [ { "gen": { "height": 960300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad260a947db43e69addfcc25055d2d57f0e0def98475fdaa7f600fb58abdd35b" } } ], "extra": [ 1, 235, 179, 11, 224, 32, 60, 194, 25, 23, 169, 228, 251, 103, 206, 207, 33, 57, 217, 8, 225, 33, 114, 247, 162, 212, 170, 165, 246, 84, 220, 110, 191, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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