← previous blocknext block →recent activity
Analyzing
Block #91,978,244
12 transactions · 10 stateful · 2026-07-31 17:41:30 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,978,244 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ea5c5d8…6814
0x34b655…2a6f
4 touches
1 conflict
0x4f41aff2…ea0a
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x9ea5c5d8…6813
0x34b655…2a6f
4 touches
1 conflict
0xaadf583b…f95c
0x34b655…2a6f
3 touches
1 conflict
0x4aaa2679…4c1d
0x34b655…2a6f
2 touches
0 conflicts
0x6d74089c…c836
0x34b655…2a6f
2 touches
0 conflicts
0x809f2ba8…89d3
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x9ea5c5d836…4d6814
Audit this contract →
← previous block·next block →recent activity