Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c538dfcf67a1b95074b2342153e7d99a6b6ec7313c7c6f381bd74c6d8c342d8

Tx prefix hash: 44e6ae16b9bb1dc5810a49fe4d0c3096e4bc95f6eef4e76fe3f81ab8e5c0823f
Tx public key: 8f2029cadc0728331f0f0f8b0de6e19f3ea759fd429d476f7e6a038b00fa77b9
Timestamp: 1707708285 Timestamp [UCT]: 2024-02-12 03:24:45 Age [y:d:h:m:s]: 00:315:00:29:36
Block: 955645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225567 RingCT/type: yes/0
Extra: 018f2029cadc0728331f0f0f8b0de6e19f3ea759fd429d476f7e6a038b00fa77b902110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4541358174556f868dcfb38dd00ea25e7505a5ec42f740bc1a0a2818cc8fb0f0 0.600000000000 1414943 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": 955655, "vin": [ { "gen": { "height": 955645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4541358174556f868dcfb38dd00ea25e7505a5ec42f740bc1a0a2818cc8fb0f0" } } ], "extra": [ 1, 143, 32, 41, 202, 220, 7, 40, 51, 31, 15, 15, 139, 13, 230, 225, 159, 62, 167, 89, 253, 66, 157, 71, 111, 126, 106, 3, 139, 0, 250, 119, 185, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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