← previous blocknext block →recent activity
Analyzing
Block #91,411,052
17 transactions · 15 stateful · 2026-07-29 18:07:13 UTC
Parallelism
59/100
Blocked
53%
Avg conflicts / tx
0.76
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,411,052 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w29w210w311w413w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1048df8e…4c9f
0x34b655…2a6f
8 touches
6 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x41f1e2e5…2edf
0x34b655…2a6f
4 touches
1 conflict
0x6f232437…749d
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 0x1048df8e7a…af4c9f
Audit this contract →
← previous block·next block →recent activity