← previous blocknext block →recent activity
Analyzing
Block #92,312,975
21 transactions · 20 stateful · 2026-08-01 21:45:00 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,312,975 · 21 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
1w02w13w04w15w06w17w29w310w011w012w217w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x267e6f2b…14f2
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x02991b41…19e6
0x34b655…2a6f
4 touches
1 conflict
0x044844a0…7418
0x34b655…2a6f
4 touches
1 conflict
0x04994ed2…9032
0x34b655…2a6f
4 touches
1 conflict
0x083ff337…401b
0x34b655…2a6f
4 touches
1 conflict
0x0bee8017…c90a
0x34b655…2a6f
4 touches
1 conflict
0x1d757195…c641
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 0x267e6f2bff…cd14f2
Audit this contract →
← previous block·next block →recent activity