← previous blocknext block →recent activity
Analyzing
Block #92,340,389
14 transactions · 13 stateful · 2026-08-02 00:02:51 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,340,389 · 14 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
2w04w15w28w210w313w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f69fba7…a65a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xff3dbbcd…5060
0x34b655…2a6f
4 touches
1 conflict
0x99775e1a…1a1a
0x34b655…2a6f
4 touches
1 conflict
0xa38eb2fc…1658
0x34b655…2a6f
4 touches
1 conflict
0xa38eb2fc…1659
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0x0f69fba799…eea65a
Audit this contract →
← previous block·next block →recent activity