Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5d433b906df95ae2b2fb1303f835359d3ee2f84b5aa2927de05ea7a83510385

Tx prefix hash: dc0fe48451b28d128eb8fb796c3047af5e84f5ba49dfc907e07ddd1af69fba8c
Tx public key: 537dea336ccb8e79addd0238aa3dab87afb2d14010523f5603d7f075cb3279e9
Timestamp: 1730517942 Timestamp [UCT]: 2024-11-02 03:25:42 Age [y:d:h:m:s]: 00:150:14:16:03
Block: 1144670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107449 RingCT/type: yes/0
Extra: 01537dea336ccb8e79addd0238aa3dab87afb2d14010523f5603d7f075cb3279e90211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd1ac5bb81982bb621a00442aa33092a25ce144c53614f766f18a9e7e5ac87c7 0.600000000000 1628945 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": 1144680, "vin": [ { "gen": { "height": 1144670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd1ac5bb81982bb621a00442aa33092a25ce144c53614f766f18a9e7e5ac87c7" } } ], "extra": [ 1, 83, 125, 234, 51, 108, 203, 142, 121, 173, 221, 2, 56, 170, 61, 171, 135, 175, 178, 209, 64, 16, 82, 63, 86, 3, 215, 240, 117, 203, 50, 121, 233, 2, 17, 0, 0, 0, 2, 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