pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#104,983,570
← previous block
next block →
recent activity
Analyzing
Block #104,983,570
12 transactions · 12 stateful · 2026-09-15 08:18:46 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#104,983,570
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
execOrders
· blocks 1
#5
execOrders
#6
updatePrices
#7
0x5acec890
#8
0x59558d29
#9
executeBatch
#10
setData
#11
execOrders
#2
matchOrders
#4
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfac3ce0…6699
0x99c7a7…8bf0
4 touches
1 conflict
0xe9e92bac…00ed
0x754704…b603
4 touches
1 conflict
0x68c08dd2…be14
0x99c7a7…8bf0
4 touches
1 conflict
0x16563faa…51a1
0x34b655…2a6f
4 touches
1 conflict
0x330e78ba…759c
0x34b655…2a6f
4 touches
1 conflict
0x53e08444…d671
0x34b655…2a6f
4 touches
1 conflict
0x67043b0b…97d7
0x34b655…2a6f
4 touches
1 conflict
0x7c216fca…20cb
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
0xdfac3ce097…826699
Audit this contract →
← previous block
·
next block →
recent activity