← previous blocknext block →recent activity
Analyzing
Block #92,274,228
19 transactions · 19 stateful · 2026-08-01 18:30:07 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,274,228 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w38w39w110w213w314w416w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9c31a7c…a75e
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x940ef645…018e
0x34b655…2a6f
6 touches
3 conflicts
0x19235b7e…17b2
0x34b655…2a6f
4 touches
1 conflict
0x31519d10…f76b
0x34b655…2a6f
4 touches
1 conflict
0x36639c6b…4d00
0x34b655…2a6f
4 touches
1 conflict
0x43969c13…cc37
0x34b655…2a6f
4 touches
1 conflict
0x6083af24…a0df
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 0xc9c31a7cd1…93a75e
Audit this contract →
← previous block·next block →recent activity