← previous blocknext block →recent activity
Analyzing
Block #91,013,237
21 transactions · 18 stateful · 2026-07-28 08:44:25 UTC
Parallelism
71/100
Blocked
28%
Avg conflicts / tx
0.38
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,013,237 · 21 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
6w07w112w213w317w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x1c1cd830…ec32
0x34b655…2a6f
6 touches
3 conflicts
0x1febc2d0…0136
0x34b655…2a6f
4 touches
1 conflict
0x3aeb946d…ff76
0x34b655…2a6f
4 touches
1 conflict
0x43a02937…4672
0x34b655…2a6f
4 touches
1 conflict
0x4e782273…1690
0x34b655…2a6f
4 touches
1 conflict
0x6ddc75c8…c0e4
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity