pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,561,326
← previous block
next block →
recent activity
Analyzing
Block #93,561,326
8 transactions · 8 stateful · 2026-08-06 06:25:52 UTC
Parallelism
50
/100
Blocked
38
%
Avg conflicts / tx
0.5
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,561,326
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xab083028
#2
execFwdPositionOps
· blocks 1
#6
forward
#7
setData
#3
execFwdPositionOps
· blocks 2
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x9ccc60f5…00f3
0x34b655…2a6f
4 touches
1 conflict
0xc9008fd2…4dbe
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x98212952…9ba6
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2db
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2dc
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
3 conflicts on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity