← previous blocknext block →recent activity
Analyzing
Block #93,359,609
26 transactions · 24 stateful · 2026-08-05 13:31:46 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,359,609 · 26 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
4w07w08w110w011w113w214w015w116w117w019w320w121w423w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xac3e4969…39e9
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x84d6407e…6fb2
0x34b655…2a6f
4 touches
1 conflict
0x9047fc79…c1ad
0x34b655…2a6f
4 touches
1 conflict
0xb6ed511f…6b68
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity