← previous blocknext block →recent activity
Analyzing
Block #93,926,399
11 transactions · 11 stateful · 2026-08-07 13:01:38 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,926,399 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7b1189e…d092
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd4230a60…bd13
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x6937e64f…90e0
0x34b655…2a6f
4 touches
1 conflict
0x88f81e37…b9dd
0x34b655…2a6f
4 touches
1 conflict
0xa3e6758f…d3ac
0x34b655…2a6f
4 touches
1 conflict
0x46279ae7…20dd
0x2b46c0…1669
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 0xc7b1189e8a…30d092
Audit this contract →
← previous block·next block →recent activity