← previous blocknext block →recent activity
Analyzing
Block #92,579,962
16 transactions · 13 stateful · 2026-08-02 20:07:43 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,579,962 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w09w111w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f6bc8db…0519
0x34b655…2a6f
6 touches
3 conflicts
0xf5f815e7…c83e
0x34b655…2a6f
4 touches
1 conflict
0xc85f42b6…6f23
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x900ed82d…e53a
0x34b655…2a6f
4 touches
1 conflict
0x3b56f79b…310f
0x34b655…2a6f
4 touches
1 conflict
0x2a53b0a1…a22d
0x34b655…2a6f
4 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
3 conflicts on slot 0x5f6bc8db1a…f60519
Audit this contract →
← previous block·next block →recent activity