pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,718,332
← previous block
next block →
recent activity
Analyzing
Block #94,718,332
10 transactions · 10 stateful · 2026-08-10 07:40:44 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,718,332
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x5acec890
· blocks 1
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#5
batchUpdate
#7
0xed82b078
#8
setData
#6
execFwdPositionOps
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
6
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe58009e8…fe3f
0x34b655…2a6f
4 touches
1 conflict
0x3601aa45…29cb
0x34b655…2a6f
4 touches
1 conflict
0x381896f8…7c44
0x34b655…2a6f
4 touches
1 conflict
0x41377979…0a18
0x34b655…2a6f
4 touches
1 conflict
0x53d526f9…1ab8
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
1 conflict on slot
0xe58009e820…f6fe3f
Audit this contract →
← previous block
·
next block →
recent activity