Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2565ec545955adff9f5cf2c323beefe9d1c13768b7a8c99761ddc2e9d38e9072

Tx prefix hash: 00a58885957bb1f3e202500f19f3cd760748201bd748b2dc0f9f8b435ebf549d
Tx public key: 98fb685db9aaa5a3e8e9a1ac256fef06874bd54fd42a9530f3c2f523843e949b
Timestamp: 1735099188 Timestamp [UCT]: 2024-12-25 03:59:48 Age [y:d:h:m:s]: 00:097:00:36:59
Block: 1182624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69117 RingCT/type: yes/0
Extra: 0198fb685db9aaa5a3e8e9a1ac256fef06874bd54fd42a9530f3c2f523843e949b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ae8a1981a1f240693ccf28b30718ecbfe2129170ac9c90f1bb64628841ffaf3 0.600000000000 1669059 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": 1182634, "vin": [ { "gen": { "height": 1182624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ae8a1981a1f240693ccf28b30718ecbfe2129170ac9c90f1bb64628841ffaf3" } } ], "extra": [ 1, 152, 251, 104, 93, 185, 170, 165, 163, 232, 233, 161, 172, 37, 111, 239, 6, 135, 75, 213, 79, 212, 42, 149, 48, 243, 194, 245, 35, 132, 62, 148, 155, 2, 17, 0, 0, 0, 3, 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