pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,926,015
← previous block
next block →
recent activity
Analyzing
Block #100,926,015
10 transactions · 9 stateful · 2026-09-01 02:44:03 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,926,015
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0x59558d29
#4
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
#7
0x6a963c6a
#8
forceVoid
#9
setData
#2
matchOrders
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec1f21ae…eedc
0x99c7a7…8bf0
4 touches
1 conflict
0xf238d135…0155
0x34b655…2a6f
4 touches
1 conflict
0x37df7523…ccbb
0x754704…b603
4 touches
1 conflict
0xa6eca5ba…4390
0x754704…b603
4 touches
1 conflict
0xf96d61f8…8fd8
0x754704…b603
4 touches
1 conflict
0x3e366689…4d73
0x99c7a7…8bf0
4 touches
1 conflict
0x266a6b2c…4376
0x34b655…2a6f
4 touches
1 conflict
0x266a6b2c…4377
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:
0x99c7a72e…c78bf0
1 conflict on slot
0xec1f21ae4c…81eedc
Audit this contract →
← previous block
·
next block →
recent activity