← previous blocknext block →recent activity
Analyzing
Block #91,012,793
12 transactions · 12 stateful · 2026-07-28 08:42:10 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,012,793 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w18w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x98834cc0…6c23
0x34b655…2a6f
6 touches
3 conflicts
0xa8dad04b…f666
0x34b655…2a6f
6 touches
3 conflicts
0xab354035…b07c
0x34b655…2a6f
6 touches
3 conflicts
0xc83b7e6b…9c68
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x56a9f59c…681d
0x34b655…2a6f
4 touches
1 conflict
0x57698337…b2b9
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