Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10665682e2a94ffb7deeab056c8cb34540560e6feeb365f64da46269515b1484

Tx prefix hash: 2e7c53db3e8fe90a1e5b3d4f121affe674c71a15d3bac55c112f5cdb48751053
Tx public key: 5a02acb9870e0e3d4a3ab5e81b68855c6bcf1384f0a103c99637c5e347919e6f
Timestamp: 1707637939 Timestamp [UCT]: 2024-02-11 07:52:19 Age [y:d:h:m:s]: 01:066:01:26:41
Block: 955064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308262 RingCT/type: yes/0
Extra: 015a02acb9870e0e3d4a3ab5e81b68855c6bcf1384f0a103c99637c5e347919e6f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83e36b409154b60cb6505500a39808a689a1f09d7c00226c5da2760423fc8880 0.600000000000 1414346 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": 955074, "vin": [ { "gen": { "height": 955064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83e36b409154b60cb6505500a39808a689a1f09d7c00226c5da2760423fc8880" } } ], "extra": [ 1, 90, 2, 172, 185, 135, 14, 14, 61, 74, 58, 181, 232, 27, 104, 133, 92, 107, 207, 19, 132, 240, 161, 3, 201, 150, 55, 197, 227, 71, 145, 158, 111, 2, 17, 0, 0, 0, 2, 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