← previous blocknext block →recent activity
Analyzing
Block #92,484,193
17 transactions · 16 stateful · 2026-08-02 12:06:05 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,484,193 · 17 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
1w02w06w17w28w312w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff196840…a453
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfc8cd993…5c11
0x34b655…2a6f
4 touches
1 conflict
0x6eb3e5af…064e
0x34b655…2a6f
4 touches
1 conflict
0x9c1a0106…de12
0x34b655…2a6f
4 touches
1 conflict
0x32790195…b240
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
6 conflicts on slot 0xff19684070…f2a453
Audit this contract →
← previous block·next block →recent activity