← previous blocknext block →recent activity
Analyzing
Block #92,588,326
21 transactions · 18 stateful · 2026-08-02 20:49:47 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,588,326 · 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
2w03w14w05w16w07w18w09w110w011w212w319w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb6334806…c949
0x34b655…2a6f
6 touches
3 conflicts
0x40970e69…da50
0x2b46c0…1669
4 touches
1 conflict
0x8cf3d245…1d0d
0x2b46c0…1669
4 touches
1 conflict
0xb05cd4f5…73d0
0x2b46c0…1669
4 touches
1 conflict
0xdb067026…9eb8
0x2b46c0…1669
4 touches
1 conflict
0x4abfb389…18f4
0x34b655…2a6f
4 touches
1 conflict
0x6598fda9…7eb7
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity