← previous blocknext block →recent activity
Analyzing
Block #92,864,439
25 transactions · 23 stateful · 2026-08-03 20:00:03 UTC
Parallelism
68/100
Blocked
48%
Avg conflicts / tx
1.2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,864,439 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w38w412w013w114w215w316w418w519w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xfb2f81c5…8916
0x34b655…2a6f
10 touches
10 conflicts
0xf79df061…e005
0xe52b14…7230
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0x408e66bb…3d6b
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: Perpl
10 conflicts on slot 0x217bd767aa…4fb79e
Audit this contract →
← previous block·next block →recent activity