← previous blocknext block →recent activity
Analyzing
Block #92,418,422
14 transactions · 11 stateful · 2026-08-02 06:35:15 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,418,422 · 14 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
5w06w07w18w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x534ef679…ae9d
0x34b655…2a6f
4 touches
1 conflict
0x7d0eaae2…60b7
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x96562bca…f07c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x651d4cdd…66a6
0x34b655…2a6f
2 touches
0 conflicts
0x651d4cdd…66a7
0x34b655…2a6f
2 touches
0 conflicts
0x698d8b5e…1fc8
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
1 conflict on slot 0x534ef679c5…43ae9d
Audit this contract →
← previous block·next block →recent activity