← previous blocknext block →recent activity
Analyzing
Block #92,751,977
14 transactions · 14 stateful · 2026-08-03 10:34:02 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,751,977 · 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
1w02w03w15w06w18w29w211w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb84f537…c9b2
0x34b655…2a6f
6 touches
3 conflicts
0x21605a79…d719
0x34b655…2a6f
6 touches
3 conflicts
0x0d2e1791…c1dd
0x34b655…2a6f
4 touches
1 conflict
0x178eeea9…53f6
0x34b655…2a6f
4 touches
1 conflict
0x1ed6aee3…3f17
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4b24f8b0…0368
0x34b655…2a6f
4 touches
1 conflict
0x50c99e05…7ce1
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 0xbb84f537ea…aec9b2
Audit this contract →
← previous block·next block →recent activity