← previous blocknext block →recent activity
Analyzing
Block #92,221,898
20 transactions · 17 stateful · 2026-08-01 14:06:54 UTC
Parallelism
80/100
Blocked
18%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,221,898 · 20 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
5w06w17w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0x8aa29f68…5645
0x34b655…2a6f
4 touches
1 conflict
0x008cda76…0020
0x34b655…2a6f
2 touches
0 conflicts
0x0883b9fc…0099
0x34b655…2a6f
2 touches
0 conflicts
0x0df5574e…d4db
0x34b655…2a6f
2 touches
0 conflicts
0x176b9cd2…048a
0x34b655…2a6f
2 touches
0 conflicts
0x21ed3831…61e5
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity