← previous blocknext block →recent activity
Analyzing
Block #91,103,878
20 transactions · 17 stateful · 2026-07-28 16:20:33 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,103,878 · 20 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
1w04w05w16w08w19w010w111w212w315w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a6bc012…7495
0x34b655…2a6f
6 touches
3 conflicts
0xb9834665…e363
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2d651956…12e8
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2db
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
3 conflicts on slot 0x9a6bc0129c…7e7495
Audit this contract →
← previous block·next block →recent activity