← previous blocknext block →recent activity
Analyzing
Block #91,997,142
16 transactions · 14 stateful · 2026-07-31 19:16:33 UTC
Parallelism
81/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,997,142 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w17w28w19w212w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b6fe4b0…478f
0x7b9256…1fb2
6 touches
3 conflicts
0x01da3c9d…30fd
0x7b9256…1fb2
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xe1f61186…e2f8
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x6b6fe4b0…478c
0x7b9256…1fb2
6 touches
3 conflicts
0x6b6fe4b0…478b
0x7b9256…1fb2
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: 0x7b9256fd…e21fb2
3 conflicts on slot 0x6b6fe4b0ae…97478f
Audit this contract →
← previous block·next block →recent activity