← previous blocknext block →recent activity
Analyzing
Block #93,855,403
10 transactions · 9 stateful · 2026-08-07 07:04:16 UTC
Parallelism
30/100
Blocked
67%
Avg conflicts / tx
2.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,855,403 · 10 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x3f63aade…5afb
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xdc8c5651…b3a7
0x34b655…2a6f
8 touches
6 conflicts
0xfd42a6b9…4c81
0x34b655…2a6f
6 touches
3 conflicts
0x43e15ca4…039d
0x34b655…2a6f
6 touches
3 conflicts
0xba9f9225…2ead
0x34b655…2a6f
6 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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity