← previous blocknext block →recent activity
Analyzing
Block #91,418,046
20 transactions · 19 stateful · 2026-07-29 18:42:26 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,418,046 · 20 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
1w02w13w04w15w26w38w09w113w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc0eb79d1…29a4
0x34b655…2a6f
6 touches
3 conflicts
0xffabb30f…8efe
0x34b655…2a6f
6 touches
3 conflicts
0x31eef44e…3694
0x34b655…2a6f
4 touches
1 conflict
0x405aba36…cc30
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5e0b8bbe…377b
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