Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fe4d9e90ee824eff5920706b4220c82a80ae0e0fd7905843bf16a2666b379f0

Tx prefix hash: 2a41322c0ebb998dc3630259a67581abfd401f9322b8b0d46e87362bba482b00
Tx public key: f5757fbf5606af4acd8587dc750afe0b5398e975b1828d68752cfa43d5b1b3c0
Timestamp: 1707864327 Timestamp [UCT]: 2024-02-13 22:45:27 Age [y:d:h:m:s]: 01:049:13:31:46
Block: 956941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296458 RingCT/type: yes/0
Extra: 01f5757fbf5606af4acd8587dc750afe0b5398e975b1828d68752cfa43d5b1b3c00211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f207ad971adfbdd92cfb3f4cda00cccd437d4a4dca72367160ed03e80b5017b 0.600000000000 1416255 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": 956951, "vin": [ { "gen": { "height": 956941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f207ad971adfbdd92cfb3f4cda00cccd437d4a4dca72367160ed03e80b5017b" } } ], "extra": [ 1, 245, 117, 127, 191, 86, 6, 175, 74, 205, 133, 135, 220, 117, 10, 254, 11, 83, 152, 233, 117, 177, 130, 141, 104, 117, 44, 250, 67, 213, 177, 179, 192, 2, 17, 0, 0, 0, 6, 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