pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,863,141
← previous block
next block →
recent activity
Analyzing
Block #92,863,141
9 transactions · 9 stateful · 2026-08-03 19:53:30 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,863,141
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 1
#3
execFwdPositionOps
#4
0x3f5c179b
#6
batchUpdate
#7
0x6a70f232
#8
setData
#2
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9834665…e363
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0a1643e3…e20d
0x34b655…2a6f
4 touches
1 conflict
0x30ccc990…afe5
0x34b655…2a6f
2 touches
0 conflicts
0x4752f576…662c
0x34b655…2a6f
2 touches
0 conflicts
0x4bfcb768…3227
0x34b655…2a6f
2 touches
0 conflicts
0x5239184c…5cfa
0x34b655…2a6f
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
0xb983466539…cee363
Audit this contract →
← previous block
·
next block →
recent activity