Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a83f8618a5cf3573d089aa93713d0e49ac3f1721ac3865c17f83e5bed8aa99c0

Tx prefix hash: 7d0da31f39dcd8ae708d5d24513464e50a4385b18f5c64c78b03bc18975b984e
Tx public key: 96219f776f2066fbb50e1c86b97ba7683ce9a354f645498dd0707067933571a0
Timestamp: 1694400534 Timestamp [UCT]: 2023-09-11 02:48:54 Age [y:d:h:m:s]: 01:168:20:04:02
Block: 845499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381747 RingCT/type: yes/0
Extra: 0196219f776f2066fbb50e1c86b97ba7683ce9a354f645498dd0707067933571a0021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.969417584000 dcy

stealth address amount amount idx
00: f5108b9582ab9ea9eeadee7b0b311d9d0376b8f4823add050db5be70bdbc30eb 0.969417584000 1298891 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": 845509, "vin": [ { "gen": { "height": 845499 } } ], "vout": [ { "amount": 969417584, "target": { "key": "f5108b9582ab9ea9eeadee7b0b311d9d0376b8f4823add050db5be70bdbc30eb" } } ], "extra": [ 1, 150, 33, 159, 119, 111, 32, 102, 251, 181, 14, 28, 134, 185, 123, 167, 104, 60, 233, 163, 84, 246, 69, 73, 141, 208, 112, 112, 103, 147, 53, 113, 160, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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