← previous blocknext block →recent activity
Analyzing
Block #91,090,149
16 transactions · 14 stateful · 2026-07-28 15:11:27 UTC
Parallelism
50/100
Blocked
64%
Avg conflicts / tx
1.19
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,090,149 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w06w37w48w111w312w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf1345bef…5530
0x34b655…2a6f
8 touches
6 conflicts
0x03d53e11…3f6f
0x34b655…2a6f
6 touches
3 conflicts
0x5c4722b6…7860
0x34b655…2a6f
6 touches
3 conflicts
0xbf68b5d2…0eba
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x781a2c9b…f540
0x34b655…2a6f
4 touches
1 conflict
0x799ef54c…4a0c
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