← previous blocknext block →recent activity
Analyzing
Block #93,389,505
24 transactions · 17 stateful · 2026-08-05 16:02:05 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,389,505 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w211w012w113w214w016w320w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388114fc…db6c
0x34b655…2a6f
8 touches
6 conflicts
0x033cf007…136d
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x02693e83…54be
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
6 touches
3 conflicts
0x388114fc…db6d
0x34b655…2a6f
6 touches
3 conflicts
0xb7482cca…fd52
0xd32edf…ff58
5 touches
3 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
6 conflicts on slot 0x388114fca1…98db6c
Audit this contract →
← previous block·next block →recent activity