Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73724ab4cc2632b0de8590fe9c5fe8db4131827aaff6213e54923a0f5d0762e5

Tx prefix hash: bb43c621f391b7c639adb3af984ecd055230cd065f1d4724d5fa7a9954bcb189
Tx public key: 97df82a90e3333fac53898f2b75ccffa1d62a3258e84054f541c5dd249bdd834
Timestamp: 1696699776 Timestamp [UCT]: 2023-10-07 17:29:36 Age [y:d:h:m:s]: 01:109:07:14:08
Block: 864587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339347 RingCT/type: yes/0
Extra: 0197df82a90e3333fac53898f2b75ccffa1d62a3258e84054f541c5dd249bdd83402110000000136a45730000000000000000000

1 output(s) for total of 0.838039323000 dcy

stealth address amount amount idx
00: 0ee5b73f4af7ee3fa61a1ba4c92bdef8441bcb0f8cf7ecdcf0809eafd117e2a2 0.838039323000 1319107 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": 864597, "vin": [ { "gen": { "height": 864587 } } ], "vout": [ { "amount": 838039323, "target": { "key": "0ee5b73f4af7ee3fa61a1ba4c92bdef8441bcb0f8cf7ecdcf0809eafd117e2a2" } } ], "extra": [ 1, 151, 223, 130, 169, 14, 51, 51, 250, 197, 56, 152, 242, 183, 92, 207, 250, 29, 98, 163, 37, 142, 132, 5, 79, 84, 28, 93, 210, 73, 189, 216, 52, 2, 17, 0, 0, 0, 1, 54, 164, 87, 48, 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