pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#104,166,476
← previous block
next block →
recent activity
Analyzing
Block #104,166,476
11 transactions · 11 stateful · 2026-09-12 11:21:22 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#104,166,476
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
0x5acec890
#4
0x5acec890
#5
0x59558d29
#6
setData
#7
execFwdPositionOpsV2
· blocks 1
#9
execFwdPositionOpsV2
#10
execOrders
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe66201d4…84f1
0x34b655…2a6f
4 touches
1 conflict
0xe7b9eede…2538
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2bfc7cbf…5fbf
0x34b655…2a6f
2 touches
0 conflicts
0x522acad4…5db3
0x34b655…2a6f
2 touches
0 conflicts
0x5ca747de…d624
0x34b655…2a6f
2 touches
0 conflicts
0x631583cf…bf21
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
0xe66201d40c…1e84f1
Audit this contract →
← previous block
·
next block →
recent activity