← previous blocknext block →recent activity
Analyzing
Block #93,682,260
6 transactions · 6 stateful · 2026-08-06 16:33:49 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,682,260 · 6 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6000ba5…8d65
0x34b655…2a6f
4 touches
1 conflict
0x07bb3f5a…617e
0x34b655…2a6f
2 touches
0 conflicts
0x1a4437ae…c776
0x34b655…2a6f
2 touches
0 conflicts
0x1cdfe548…d3aa
0x34b655…2a6f
2 touches
0 conflicts
0x1e0c5c66…74d9
0x34b655…2a6f
2 touches
0 conflicts
0x428b6e5b…8909
0x34b655…2a6f
2 touches
0 conflicts
0x434a99da…6442
0x34b655…2a6f
2 touches
0 conflicts
0x45911da6…5523
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 0xc6000ba5c1…988d65
Audit this contract →
← previous block·next block →recent activity