← previous blocknext block →recent activity
Analyzing
Block #91,398,456
14 transactions · 11 stateful · 2026-07-29 17:03:30 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,398,456 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w19w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefcdf197…96a2
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xd2648804…deff
0x34b655…2a6f
4 touches
1 conflict
0x090fdd1e…47aa
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xb56f0740…7542
0x34b655…2a6f
4 touches
1 conflict
0x8972e24b…5d77
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0xefcdf19725…1096a2
Audit this contract →
← previous block·next block →recent activity