← previous blocknext block →recent activity
Analyzing
Block #92,858,602
23 transactions · 23 stateful · 2026-08-03 19:30:40 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,858,602 · 23 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
1w03w04w05w18w211w312w015w116w117w318w420w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c7f2eca…cf5e
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x6459805c…615d
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
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 0x1c7f2eca4a…e4cf5e
Audit this contract →
← previous block·next block →recent activity