← previous blocknext block →recent activity
Analyzing
Block #92,587,341
16 transactions · 14 stateful · 2026-08-02 20:44:50 UTC
Parallelism
56/100
Blocked
43%
Avg conflicts / tx
1.31
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,587,341 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w38w49w510w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc85f42b6…6f23
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0x2648406a…d91d
0x34b655…2a6f
10 touches
10 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0x9b9e2a0b…0498
0x34b655…2a6f
6 touches
3 conflicts
0x1c8753e8…d214
0x34b655…2a6f
6 touches
3 conflicts
0x35b0198e…3e0d
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
21 conflicts on slot 0xc85f42b605…b36f23
Audit this contract →
← previous block·next block →recent activity