← previous blocknext block →recent activity
Analyzing
Block #91,041,165
24 transactions · 23 stateful · 2026-07-28 11:04:58 UTC
Parallelism
79/100
Blocked
26%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,041,165 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w110w011w113w014w117w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x57b02276…db3f
0x34b655…2a6f
6 touches
3 conflicts
0x2a5e2b11…1c2b
0x34b655…2a6f
6 touches
3 conflicts
0x831625ad…c485
0x34b655…2a6f
6 touches
3 conflicts
0x251e4ed8…a3f4
0x34b655…2a6f
6 touches
3 conflicts
0x4e94a6f3…ceac
0x34b655…2a6f
4 touches
1 conflict
0x6459805c…615d
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity