← previous blocknext block →recent activity
Analyzing
Block #92,201,674
8 transactions · 7 stateful · 2026-08-01 12:25:12 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,201,674 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x09396f14…669f
0x34b655…2a6f
2 touches
0 conflicts
0x0a6a5b44…d0e5
0x34b655…2a6f
2 touches
0 conflicts
0x0df5574e…d4db
0x34b655…2a6f
2 touches
0 conflicts
0x1a843f41…02aa
0x34b655…2a6f
2 touches
0 conflicts
0x27034002…2f27
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity