← previous blocknext block →recent activity
Analyzing
Block #92,340,509
15 transactions · 11 stateful · 2026-08-02 00:03:27 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,340,509 · 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
7w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x705ab4ae…0162
0x34b655…2a6f
5 touches
3 conflicts
0x949c0ded…5cd3
0x34b655…2a6f
5 touches
3 conflicts
0x518aa708…c018
0x34b655…2a6f
4 touches
1 conflict
0xf8857df5…9a36
0x34b655…2a6f
4 touches
1 conflict
0xa060b594…669d
0x754704…b603
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
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity