← previous blocknext block →recent activity
Analyzing
Block #92,358,064
16 transactions · 16 stateful · 2026-08-02 01:31:44 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,358,064 · 16 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
1w02w13w04w15w27w38w49w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b55198a…b946
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x27d6168e…7c5e
0x34b655…2a6f
4 touches
1 conflict
0x52c14416…1e5a
0x34b655…2a6f
4 touches
1 conflict
0x68a2902c…b23f
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x83d939c6…4c36
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
3 conflicts on slot 0x7b55198a70…73b946
Audit this contract →
← previous block·next block →recent activity