← previous blocknext block →recent activity
Analyzing
Block #92,768,464
28 transactions · 26 stateful · 2026-08-03 11:57:01 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.54
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,768,464 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w09w010w115w117w018w119w221w322w423w524w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68caa37b…c795
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x743061ce…a4ac
0x34b655…2a6f
6 touches
3 conflicts
0x7b80de04…86d1
0x34b655…2a6f
6 touches
3 conflicts
0x557908f3…a476
0x34b655…2a6f
4 touches
1 conflict
0x56984f2c…9465
0x34b655…2a6f
4 touches
1 conflict
0x6a634b22…80d3
0x34b655…2a6f
4 touches
1 conflict
0x75899c31…a2e0
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 0x68caa37b30…f7c795
Audit this contract →
← previous block·next block →recent activity