← previous blocknext block →recent activity
Analyzing
Block #91,069,682
24 transactions · 21 stateful · 2026-07-28 13:28:25 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.75
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,069,682 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w412w515w616w017w120w022w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x6e6b8ec7…2197
0x34b655…2a6f
8 touches
6 conflicts
0x1ebb35bb…ef2a
0x34b655…2a6f
4 touches
1 conflict
0x36b7c966…ba5c
0x34b655…2a6f
4 touches
1 conflict
0x3d22c439…de6d
0x34b655…2a6f
4 touches
1 conflict
0x540e42f5…19e1
0x34b655…2a6f
4 touches
1 conflict
0x63ac310a…f307
0x34b655…2a6f
4 touches
1 conflict
0x73f1f4e4…45e5
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