← previous blocknext block →recent activity
Analyzing
Block #92,686,962
11 transactions · 11 stateful · 2026-08-03 05:06:45 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,686,962 · 11 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
1w02w14w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68a2902c…b23f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x1fd19887…8e0e
0x34b655…2a6f
4 touches
1 conflict
0xf0833c8c…53db
0x34b655…2a6f
4 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0x3c78ca04…432c
0x34b655…2a6f
2 touches
0 conflicts
0x53bda555…3810
0x34b655…2a6f
2 touches
0 conflicts
0x5ddfc90a…de81
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
3 conflicts on slot 0x68a2902c52…e3b23f
Audit this contract →
← previous block·next block →recent activity