← previous blocknext block →recent activity
Analyzing
Block #91,086,832
24 transactions · 20 stateful · 2026-07-28 14:54:45 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,086,832 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w08w19w212w314w016w119w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
6 touches
3 conflicts
0x61589664…4bd6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6f6b4878…d72d
0x34b655…2a6f
4 touches
1 conflict
0x9d9bed71…d466
0x34b655…2a6f
4 touches
1 conflict
0xf1a4f963…62b5
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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: 0x48cba278…e2b48b
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity