Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e63aa99e56adb11d1d1effb895fd560620259fcb96e3da4f818b9b4e6cbf9e1b

Tx prefix hash: 87931d0fccba84b140d25f8791d3811a7ba6857caf9c3d287d3ecb9e8876dfc6
Tx public key: 889caf22d84478c5ce42b30d0ddef6c1cf0938526513e6dd891a047c06f79e0b
Timestamp: 1694318074 Timestamp [UCT]: 2023-09-10 03:54:34 Age [y:d:h:m:s]: 02:085:07:51:35
Block: 844818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 580709 RingCT/type: yes/0
Extra: 01889caf22d84478c5ce42b30d0ddef6c1cf0938526513e6dd891a047c06f79e0b0211000000054b8f5122000000000000000000

1 output(s) for total of 0.974467433000 dcy

stealth address amount amount idx
00: 8ff0a759a9e9cbfdbc377f0efa9188a36464a585605129b5bcb6e4fe94ba3b6f 0.974467433000 1298150 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": 844828, "vin": [ { "gen": { "height": 844818 } } ], "vout": [ { "amount": 974467433, "target": { "key": "8ff0a759a9e9cbfdbc377f0efa9188a36464a585605129b5bcb6e4fe94ba3b6f" } } ], "extra": [ 1, 136, 156, 175, 34, 216, 68, 120, 197, 206, 66, 179, 13, 13, 222, 246, 193, 207, 9, 56, 82, 101, 19, 230, 221, 137, 26, 4, 124, 6, 247, 158, 11, 2, 17, 0, 0, 0, 5, 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