← previous blocknext block →recent activity
Analyzing
Block #92,770,248
15 transactions · 14 stateful · 2026-08-03 12:05:59 UTC
Parallelism
87/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,770,248 · 15 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
5w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcfcb676f…2deb
0x34b655…2a6f
4 touches
1 conflict
0x0aa54240…f89e
0x34b655…2a6f
4 touches
1 conflict
0x0cb11f1d…83c0
0x34b655…2a6f
4 touches
1 conflict
0xcfcb676f…2dea
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x326f2a00…a2a6
0x34b655…2a6f
4 touches
1 conflict
0xb91a6f59…722c
0x34b655…2a6f
4 touches
1 conflict
0x247b3fd4…b1ec
0x34b655…2a6f
3 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
1 conflict on slot 0xcfcb676f70…b22deb
Audit this contract →
← previous block·next block →recent activity