Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce43375efbbc64d92968f703f6f88be8fe3c52cfd6cb8d5178b237cb01e6d797

Tx prefix hash: a7fbcb7bad962d3936b387eb8a4da07b458bb056015dac6e6162122f60477c7e
Tx public key: 764c9ed2cd833f0db132d7f864766864f49f685630a56dcf9ef8f795e90554e8
Timestamp: 1720707397 Timestamp [UCT]: 2024-07-11 14:16:37 Age [y:d:h:m:s]: 00:287:09:41:14
Block: 1063432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205348 RingCT/type: yes/0
Extra: 01764c9ed2cd833f0db132d7f864766864f49f685630a56dcf9ef8f795e90554e802110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be66dbb1f4d72661b144c0aa1da8df1a8c4a75971801dd728466042b2b5991bf 0.600000000000 1533947 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": 1063442, "vin": [ { "gen": { "height": 1063432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be66dbb1f4d72661b144c0aa1da8df1a8c4a75971801dd728466042b2b5991bf" } } ], "extra": [ 1, 118, 76, 158, 210, 205, 131, 63, 13, 177, 50, 215, 248, 100, 118, 104, 100, 244, 159, 104, 86, 48, 165, 109, 207, 158, 248, 247, 149, 233, 5, 84, 232, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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