← previous blocknext block →recent activity
Analyzing
Block #91,211,945
16 transactions · 16 stateful · 2026-07-29 01:24:09 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,211,945 · 16 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
1w02w14w05w16w27w38w29w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xefcdf197…96a2
0x34b655…2a6f
6 touches
3 conflicts
0xf199b4ad…12d3
0xd32edf…ff58
5 touches
3 conflicts
0xb176789b…c34b
0x34b655…2a6f
4 touches
1 conflict
0xb5b879be…8943
0x34b655…2a6f
4 touches
1 conflict
0xd86cd5ce…ffed
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x1a58d21d…2419
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity