Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ea6c552baaa1cc2a2d3bbb327e858e1124644750c36be14b6e9706ffe70f81b

Tx prefix hash: 097fbe58e245e301827c978ec824d2cbaf30a2f6b1409841ef6ea63510ce5d3b
Tx public key: a171103fc9a7f3828bf4f5c7b4b8d9c46ff30c8bf57bfe0e9d27d27aaebdb177
Timestamp: 1720198891 Timestamp [UCT]: 2024-07-05 17:01:31 Age [y:d:h:m:s]: 01:127:07:43:20
Block: 1059194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349537 RingCT/type: yes/0
Extra: 01a171103fc9a7f3828bf4f5c7b4b8d9c46ff30c8bf57bfe0e9d27d27aaebdb1770211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f4c21f7f0f4b434e7af4580076936241b50ee02f7522666dfdd4329af76b2c6 0.600000000000 1529659 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": 1059204, "vin": [ { "gen": { "height": 1059194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f4c21f7f0f4b434e7af4580076936241b50ee02f7522666dfdd4329af76b2c6" } } ], "extra": [ 1, 161, 113, 16, 63, 201, 167, 243, 130, 139, 244, 245, 199, 180, 184, 217, 196, 111, 243, 12, 139, 245, 123, 254, 14, 157, 39, 210, 122, 174, 189, 177, 119, 2, 17, 0, 0, 0, 4, 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