Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be8b855b53977febe1b21e80005c54455233b3c5b540f9e250c51e93db40ab3a

Tx prefix hash: 8154c17b4b039e99e904badef42dd5c8162df6030ea2cc4d8dcaae8b672c5aab
Tx public key: 31abf7ccb566207c7b4fe9c3b0d49911fd14d8e5f1498394b8d77d9efad371e8
Timestamp: 1695775924 Timestamp [UCT]: 2023-09-27 00:52:04 Age [y:d:h:m:s]: 01:203:09:41:21
Block: 856928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406431 RingCT/type: yes/0
Extra: 0131abf7ccb566207c7b4fe9c3b0d49911fd14d8e5f1498394b8d77d9efad371e80211000000044b8f5122000000000000000000

1 output(s) for total of 0.888468132000 dcy

stealth address amount amount idx
00: c455a36bcdae5f57b9c0a3e66c803d544370f043c51e0e1f5fca6f8c899ec741 0.888468132000 1311026 of 0

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": 856938, "vin": [ { "gen": { "height": 856928 } } ], "vout": [ { "amount": 888468132, "target": { "key": "c455a36bcdae5f57b9c0a3e66c803d544370f043c51e0e1f5fca6f8c899ec741" } } ], "extra": [ 1, 49, 171, 247, 204, 181, 102, 32, 124, 123, 79, 233, 195, 176, 212, 153, 17, 253, 20, 216, 229, 241, 73, 131, 148, 184, 215, 125, 158, 250, 211, 113, 232, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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