Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1714d13eafcf6c1f0cfcb435e6e1d2c98c69d295e17c5cf2ad56552c91e2ebd0

Tx prefix hash: c1dea3a385797365a453bb63dd8d543c41bf491cf4967e3068661f574cbb222f
Tx public key: 1752381b3b79c918bff5fdfe13602b5910048be7db1e6c87b6a09fb402f441de
Timestamp: 1723748657 Timestamp [UCT]: 2024-08-15 19:04:17 Age [y:d:h:m:s]: 00:129:10:37:40
Block: 1088637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92625 RingCT/type: yes/0
Extra: 011752381b3b79c918bff5fdfe13602b5910048be7db1e6c87b6a09fb402f441de0211000000f3e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a72f945b37b721edd12849de5c003a614d53022c8d0af96406ab9a6c5289733d 0.600000000000 1563254 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": 1088647, "vin": [ { "gen": { "height": 1088637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a72f945b37b721edd12849de5c003a614d53022c8d0af96406ab9a6c5289733d" } } ], "extra": [ 1, 23, 82, 56, 27, 59, 121, 201, 24, 191, 245, 253, 254, 19, 96, 43, 89, 16, 4, 139, 231, 219, 30, 108, 135, 182, 160, 159, 180, 2, 244, 65, 222, 2, 17, 0, 0, 0, 243, 233, 20, 221, 21, 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