← previous blocknext block →recent activity
Analyzing
Block #92,299,453
12 transactions · 12 stateful · 2026-08-01 20:36:59 UTC
Parallelism
58/100
Blocked
58%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,299,453 · 12 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
1w02w13w04w15w06w17w29w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4c04ce68…d007
0x34b655…2a6f
6 touches
3 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x0af22aa9…087c
0x34b655…2a6f
4 touches
1 conflict
0x0b35df1d…7c83
0x34b655…2a6f
4 touches
1 conflict
0x0f427418…2a49
0x34b655…2a6f
4 touches
1 conflict
0x1bd69a6a…2b8a
0x34b655…2a6f
4 touches
1 conflict
0x2d071de0…c86e
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity