← previous blocknext block →recent activity
Analyzing
Block #92,348,843
15 transactions · 14 stateful · 2026-08-02 00:45:22 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,348,843 · 15 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
2w04w15w29w310w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f6aef87…8137
0x34b655…2a6f
6 touches
3 conflicts
0xe1f61186…e2f8
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x5921a85d…05a3
0x7b9256…1fb2
6 touches
3 conflicts
0x5921a85d…05a4
0x7b9256…1fb2
6 touches
3 conflicts
0x5921a85d…05a7
0x7b9256…1fb2
6 touches
3 conflicts
0xc0cbb4f7…234e
0x7b9256…1fb2
6 touches
3 conflicts
0xc0cbb4f7…234f
0x7b9256…1fb2
6 touches
3 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
3 conflicts on slot 0x0f6aef8771…dd8137
Audit this contract →
← previous block·next block →recent activity