← previous blocknext block →recent activity
Analyzing
Block #93,576,112
14 transactions · 12 stateful · 2026-08-06 07:40:11 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,576,112 · 14 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9baf4912…5f0f
0x34b655…2a6f
4 touches
1 conflict
0xa467a677…b3b5
0x34b655…2a6f
4 touches
1 conflict
0x04e17b28…d9f0
0x34b655…2a6f
4 touches
1 conflict
0x72d578ba…29fb
0x34b655…2a6f
4 touches
1 conflict
0x04e17b28…d9ef
0x34b655…2a6f
4 touches
1 conflict
0x89dd6a50…6d56
0x34b655…2a6f
4 touches
1 conflict
0x4d4b9ce9…6831
0x34b655…2a6f
2 touches
0 conflicts
0x6f132c01…cdcc
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 0x9baf491295…825f0f
Audit this contract →
← previous block·next block →recent activity