← previous blocknext block →recent activity
Analyzing
Block #92,821,956
14 transactions · 12 stateful · 2026-08-03 16:26:08 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,821,956 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w09w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bcdd4a1…3d3a
0x34b655…2a6f
4 touches
1 conflict
0xd81dbbb9…d0c5
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 conflicts
0x7f4a8466…f2cc
0x2b46c0…1669
2 touches
0 conflicts
0x0110331c…b891
0x34b655…2a6f
2 touches
0 conflicts
0x329de4eb…2981
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x2bcdd4a12e…6b3d3a
Audit this contract →
← previous block·next block →recent activity