Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdc6b9956171a960a84afaa31ab7cbdc2567dfc3e910e384cf6ff17077e6ab61

Tx prefix hash: dc68f61c64cf3a5f2384425204e00e7a9860bd52d2ea5f6f20885e0c9eafe6a2
Tx public key: a6d759a3fc580d0ea6dcf83a3af94dc1d01b0f322d4ea21aab7f8fb013001f6b
Timestamp: 1732535446 Timestamp [UCT]: 2024-11-25 11:50:46 Age [y:d:h:m:s]: 00:144:03:07:06
Block: 1161381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102837 RingCT/type: yes/0
Extra: 01a6d759a3fc580d0ea6dcf83a3af94dc1d01b0f322d4ea21aab7f8fb013001f6b021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd2036746bc666ee8358741d4af18b3cfd5bc7189ecab345d99166987dc95aa7 0.600000000000 1647034 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": 1161391, "vin": [ { "gen": { "height": 1161381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd2036746bc666ee8358741d4af18b3cfd5bc7189ecab345d99166987dc95aa7" } } ], "extra": [ 1, 166, 215, 89, 163, 252, 88, 13, 14, 166, 220, 248, 58, 58, 249, 77, 193, 208, 27, 15, 50, 45, 78, 162, 26, 171, 127, 143, 176, 19, 0, 31, 107, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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