← previous blocknext block →recent activity
Analyzing
Block #93,242,797
16 transactions · 14 stateful · 2026-08-05 03:44:27 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,242,797 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c69390f…0832
0x34b655…2a6f
4 touches
1 conflict
0xa2a6161a…c202
0x34b655…2a6f
4 touches
1 conflict
0xa67102b1…9837
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xdbc62196…3245
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x13978b18…bb8c
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0x9c69390f79…120832
Audit this contract →
← previous block·next block →recent activity