← previous blocknext block →recent activity
Analyzing
Block #92,340,400
12 transactions · 12 stateful · 2026-08-02 00:02:54 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,340,400 · 12 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
2w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc1d2d0e5…3299
0x09475a…400f
2 touches
0 conflicts
0x5cdc8924…c0f1
0x10aeaf…5417
2 touches
0 conflicts
0x7f5b2c1d…0e7f
0x34b655…2a6f
2 touches
0 conflicts
0x948836ff…59ab
0x34b655…2a6f
2 touches
0 conflicts
0x9563b01c…92b4
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 0x3e6302c867…b164f5
Audit this contract →
← previous block·next block →recent activity