← previous blocknext block →recent activity
Analyzing
Block #91,433,804
10 transactions · 9 stateful · 2026-07-29 20:02:35 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,433,804 · 10 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
4w05w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda2ee2e7…968a
0x34b655…2a6f
4 touches
1 conflict
0xf83b23f9…5a2e
0x34b655…2a6f
4 touches
1 conflict
0xf5eca2af…265a
0x34b655…2a6f
3 touches
1 conflict
0x5ac64f90…04c6
0x34b655…2a6f
3 touches
1 conflict
0xbfe7fd3a…3168
0x3bd359…433a
2 touches
0 conflicts
0x97d1efdc…77f3
0x57ea24…2cec
2 touches
0 conflicts
0xa33a4377…4940
0x57ea24…2cec
2 touches
0 conflicts
0x2d360b55…d4f5
0x80f006…d585
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 0xda2ee2e777…e7968a
Audit this contract →
← previous block·next block →recent activity