← previous blocknext block →recent activity
Analyzing
Block #91,408,927
8 transactions · 7 stateful · 2026-07-29 17:56:26 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,408,927 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d38e3ab…a8f6
0x34b655…2a6f
4 touches
1 conflict
0x65977bc0…2640
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x061128e3…b2f8
0x34b655…2a6f
2 touches
0 conflicts
0x164b7e99…e472
0x34b655…2a6f
2 touches
0 conflicts
0x27034002…2f27
0x34b655…2a6f
2 touches
0 conflicts
0x50dfdd6a…fc6a
0x34b655…2a6f
2 touches
0 conflicts
0x6eb3904d…4bfb
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x0d38e3ab0f…4da8f6
Audit this contract →
← previous block·next block →recent activity