Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f75a48dc101183536cf56c91537eb620fe3aee178a0b0b38a90d2d38f11e914c

Tx prefix hash: afe4f983f26967339fd634f6fabf40121a35844c6bd2ecfa0cae4bcaf8259938
Tx public key: a1da6fdd4fb296ef9a38840ecfaa1e334c8e9bf93fd8f27495ced7ac19fa9c29
Timestamp: 1711122344 Timestamp [UCT]: 2024-03-22 15:45:44 Age [y:d:h:m:s]: 00:361:19:53:13
Block: 983977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258698 RingCT/type: yes/0
Extra: 01a1da6fdd4fb296ef9a38840ecfaa1e334c8e9bf93fd8f27495ced7ac19fa9c290211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e0f3df89523880b50fbd17d5c959ee1fd64a8d3a5abdb1511335afb1dc90364 0.600000000000 1444130 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": 983987, "vin": [ { "gen": { "height": 983977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e0f3df89523880b50fbd17d5c959ee1fd64a8d3a5abdb1511335afb1dc90364" } } ], "extra": [ 1, 161, 218, 111, 221, 79, 178, 150, 239, 154, 56, 132, 14, 207, 170, 30, 51, 76, 142, 155, 249, 63, 216, 242, 116, 149, 206, 215, 172, 25, 250, 156, 41, 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