pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,027,158
← previous block
next block →
recent activity
Analyzing
Block #100,027,158
11 transactions · 10 stateful · 2026-08-28 23:17:05 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,027,158
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0xab083028
#3
execOrders
#4
0x5acec890
#5
0x928e4afa
· blocks 1
#6
0x59558d29
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#10
setData
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1731f0f…1f9d
0x34b655…2a6f
4 touches
1 conflict
0xfc801da8…bb7a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xf69c30e6…81e3
0x2b46c0…1669
2 touches
0 conflicts
0x038b9243…553d
0x34b655…2a6f
2 touches
0 conflicts
0x4a39a2a4…857b
0x34b655…2a6f
2 touches
0 conflicts
0x5060cdde…445d
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
0xa1731f0fa4…fc1f9d
Audit this contract →
← previous block
·
next block →
recent activity