← previous blocknext block →recent activity
Analyzing
Block #91,403,517
23 transactions · 22 stateful · 2026-07-29 17:29:02 UTC
Parallelism
57/100
Blocked
64%
Avg conflicts / tx
1.39
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,403,517 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w07w18w29w210w311w112w414w515w616w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb44407fb…9b00
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x5d1ac445…5233
0x34b655…2a6f
6 touches
3 conflicts
0x1f396cee…862f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
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
15 conflicts on slot 0xb44407fb1f…649b00
Audit this contract →
← previous block·next block →recent activity