pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,177,535
← previous block
next block →
recent activity
Analyzing
Block #102,177,535
14 transactions · 13 stateful · 2026-09-05 11:51:52 UTC
Parallelism
86
/100
Blocked
15
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,177,535
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0xab083028
#4
0xab083028
#5
updatePrices
#6
0x5acec890
#7
0x5acec890
· blocks 1
#8
0x5acec890
#9
execOrder
#10
0x59558d29
#11
setData
#12
transfer
#2
matchOrders
#13
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68c08dd2…be14
0x99c7a7…8bf0
4 touches
1 conflict
0xdfac3ce0…6699
0x99c7a7…8bf0
4 touches
1 conflict
0x00532bf5…5711
0x754704…b603
4 touches
1 conflict
0x0eff0903…8165
0x754704…b603
4 touches
1 conflict
0xe9e92bac…00ed
0x754704…b603
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x2eb15031…f48d
0x34b655…2a6f
2 touches
0 conflicts
0x44ab8c0b…6b4b
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:
0x99c7a72e…c78bf0
1 conflict on slot
0x68c08dd231…8fbe14
Audit this contract →
← previous block
·
next block →
recent activity