pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#103,987,142
← previous block
next block →
recent activity
Analyzing
Block #103,987,142
12 transactions · 11 stateful · 2026-09-11 20:09:04 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#103,987,142
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x000001e4
· blocks 1
#3
0xab083028
#4
0x5acec890
#5
execute
#6
0x59558d29
#8
setData
#9
execFwdPositionOpsV2
· blocks 1
#11
0x1d9fe9…4a31
#7
0x0d04188d
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0xfe53cc…ee89
4 touches
1 conflict
0xab161cd0…c92d
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x23501896…00dd
0x3bd359…433a
4 touches
1 conflict
0x00000000…000a
0x3d80f5…41b3
4 touches
1 conflict
0x2c32b289…87c2
0x3d80f5…41b3
4 touches
1 conflict
0x1bb87379…1b85
0xa9da3c…540f
4 touches
1 conflict
0xba9741c5…b632
0xa9da3c…540f
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:
0xfe53ccbb…43ee89
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity