← previous blocknext block →recent activity
Analyzing
Block #91,124,386
45 transactions · 38 stateful · 2026-07-28 18:03:42 UTC
Parallelism
69/100
Blocked
79%
Avg conflicts / tx
2.8
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #91,124,386 · 45 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w27w38w211w012w113w214w315w416w517w618w719w820w921w1028w329w232w333w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
28 touches
91 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
8 touches
6 conflicts
0x89678d1b…463e
0xa6afd3…d132
8 touches
6 conflicts
0x439cfb2c…7b9e
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
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: 0x48cba278…e2b48b
91 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity