← previous blocknext block →recent activity
Analyzing
Block #92,854,244
14 transactions · 14 stateful · 2026-08-03 19:08:43 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,854,244 · 14 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
1w02w13w04w18w29w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28ceceef…ecc2
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf3d46eb2…d46b
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xd79c9727…1233
0x34b655…2a6f
6 touches
3 conflicts
0x51c18152…f628
0x34b655…2a6f
4 touches
1 conflict
0x9cf9008a…d826
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
10 conflicts on slot 0x28ceceefb3…22ecc2
Audit this contract →
← previous block·next block →recent activity