← previous blocknext block →recent activity
Analyzing
Block #92,286,239
18 transactions · 16 stateful · 2026-08-01 19:30:31 UTC
Parallelism
72/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,286,239 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w16w27w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f93d1d7…914a
0x34b655…2a6f
6 touches
3 conflicts
0xf06ab8d8…3589
0x34b655…2a6f
6 touches
3 conflicts
0x0216a577…5bd8
0x34b655…2a6f
4 touches
1 conflict
0x0793341d…0b4e
0x34b655…2a6f
4 touches
1 conflict
0xfb67be15…a190
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xd9129ff6…6786
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
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
3 conflicts on slot 0x2f93d1d73d…c9914a
Audit this contract →
← previous block·next block →recent activity