pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,771,780
← previous block
next block →
recent activity
Analyzing
Block #92,771,780
10 transactions · 9 stateful · 2026-08-03 12:13:41 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,771,780
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0x0f6795d9
#3
0x0f6795d9
· blocks 1
#4
updateDataFeedsValuesPartial
#6
0xed82b078
#7
setData
#8
withdraw
#9
0x59558d29
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea559e7b…41f4
0x34b655…2a6f
4 touches
1 conflict
0xa0eed989…dd7a
0x34b655…2a6f
4 touches
1 conflict
0x19795ad6…4a16
0x34b655…2a6f
4 touches
1 conflict
0x041d450f…d3f8
0x34b655…2a6f
2 touches
0 conflicts
0x171ff85b…255e
0x34b655…2a6f
2 touches
0 conflicts
0x1efc452b…354f
0x34b655…2a6f
2 touches
0 conflicts
0x1efc452b…3550
0x34b655…2a6f
2 touches
0 conflicts
0x4f1e16d4…4833
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
0xea559e7b33…d641f4
Audit this contract →
← previous block
·
next block →
recent activity