Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b379e8805452ca60ab4b9f1f39d89266f63c728a71fa18209df0f2da3c1e9ba1

Tx prefix hash: 6989c75eab484b6fefc843599608537c76d8d756fb170ef3962178ea654a3e68
Tx public key: 3594faf5ee5af8ba4cde750dd29a249f8fac4e62089edcfcf33f8b812bb89a27
Timestamp: 1726408529 Timestamp [UCT]: 2024-09-15 13:55:29 Age [y:d:h:m:s]: 00:058:23:52:20
Block: 1110685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42176 RingCT/type: yes/0
Extra: 013594faf5ee5af8ba4cde750dd29a249f8fac4e62089edcfcf33f8b812bb89a27021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8954d4538844e56e73b78ad4726f9c3f751c396a1d0ea8a9d1713b9bb97ed262 0.600000000000 1589376 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": 1110695, "vin": [ { "gen": { "height": 1110685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8954d4538844e56e73b78ad4726f9c3f751c396a1d0ea8a9d1713b9bb97ed262" } } ], "extra": [ 1, 53, 148, 250, 245, 238, 90, 248, 186, 76, 222, 117, 13, 210, 154, 36, 159, 143, 172, 78, 98, 8, 158, 220, 252, 243, 63, 139, 129, 43, 184, 154, 39, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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