← previous blocknext block →recent activity
Analyzing
Block #93,581,334
19 transactions · 17 stateful · 2026-08-06 08:06:26 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,581,334 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w29w310w211w312w414w518w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac28c0f0…79c2
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
4 touches
1 conflict
0xb566e26f…6d5d
0x34b655…2a6f
4 touches
1 conflict
0x6b89ce6f…cc35
0x34b655…2a6f
4 touches
1 conflict
0x7da6eb60…b34e
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
6 conflicts on slot 0xac28c0f0b1…8679c2
Audit this contract →
← previous block·next block →recent activity