← previous blocknext block →recent activity
Analyzing
Block #92,567,115
15 transactions · 14 stateful · 2026-08-02 19:03:05 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,567,115 · 15 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
2w04w15w27w29w210w312w013w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7d36805…6bb8
0x34b655…2a6f
6 touches
3 conflicts
0x620b761c…270e
0x34b655…2a6f
6 touches
3 conflicts
0xf1345bef…5530
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x9ac63ae6…23c9
0x34b655…2a6f
4 touches
1 conflict
0x9ebe2892…e481
0x34b655…2a6f
4 touches
1 conflict
0xa4631748…0876
0x34b655…2a6f
4 touches
1 conflict
0xb2fa1675…4e07
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 0xa7d368051f…dc6bb8
Audit this contract →
← previous block·next block →recent activity