← previous blocknext block →recent activity
Analyzing
Block #91,969,171
23 transactions · 21 stateful · 2026-07-31 16:55:52 UTC
Parallelism
74/100
Blocked
43%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,969,171 · 23 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
1w05w17w18w212w214w016w117w218w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f2d78b1…7363
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x9eb3f337…159c
0x34b655…2a6f
6 touches
3 conflicts
0xeafd66de…0faf
0x34b655…2a6f
6 touches
3 conflicts
0x5e2aa1dd…83c9
0x34b655…2a6f
4 touches
1 conflict
0x0a278da2…7b54
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 0x0f2d78b1bb…5e7363
Audit this contract →
← previous block·next block →recent activity