← previous blocknext block →recent activity
Analyzing
Block #91,423,276
20 transactions · 19 stateful · 2026-07-29 19:08:44 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,423,276 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w28w310w311w412w414w115w216w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd42a6b9…4c81
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x3d158563…8713
0x34b655…2a6f
6 touches
3 conflicts
0x38c6ff01…689f
0x34b655…2a6f
4 touches
1 conflict
0x410c23da…5793
0x34b655…2a6f
4 touches
1 conflict
0x47729858…a47c
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 0xfd42a6b911…394c81
Audit this contract →
← previous block·next block →recent activity