Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11fed6ea1df2fc3d5e0cbb1d4e287d7714cb39c1bafd2c56a858cc9382429e84

Tx prefix hash: 758e0f67e098d27f0926bd52cfe9fefb112c1866a75ef08e317f6d47d32039fa
Tx public key: fba5e1809f56714d608429219f4344235f089028c8ca5acb4424cc5187498a95
Timestamp: 1710581875 Timestamp [UCT]: 2024-03-16 09:37:55 Age [y:d:h:m:s]: 01:039:12:29:18
Block: 979497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289223 RingCT/type: yes/0
Extra: 01fba5e1809f56714d608429219f4344235f089028c8ca5acb4424cc5187498a950211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f12e39ae8f01fd413e2a6b5748fa71e43849a26050c75f4f667ee0aeee3b3ac 0.600000000000 1439530 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": 979507, "vin": [ { "gen": { "height": 979497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f12e39ae8f01fd413e2a6b5748fa71e43849a26050c75f4f667ee0aeee3b3ac" } } ], "extra": [ 1, 251, 165, 225, 128, 159, 86, 113, 77, 96, 132, 41, 33, 159, 67, 68, 35, 95, 8, 144, 40, 200, 202, 90, 203, 68, 36, 204, 81, 135, 73, 138, 149, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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