pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,855,027
← previous block
next block →
recent activity
Analyzing
Block #99,855,027
13 transactions · 13 stateful · 2026-08-28 08:49:48 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,855,027
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updatePrices
#3
0x6ad2e98b
#4
0xab083028
#5
execOrders
#6
0x5acec890
#7
0x59558d29
#8
execFwdPositionOpsV2
· blocks 1
#9
0x3f5c179b
#11
transfer
#12
setData
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc5fc032…8d7e
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x5fde4971…aac9
0x34b655…2a6f
4 touches
1 conflict
0xbc5fc032…8d7d
0x34b655…2a6f
4 touches
1 conflict
0xd9d0b0b5…32f5
0x34b655…2a6f
3 touches
1 conflict
0xe1460710…5a8c
0x34b655…2a6f
3 touches
1 conflict
0x00532bf5…5711
0x754704…b603
2 touches
0 conflicts
0x0eff0903…8165
0x754704…b603
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
0xbc5fc032c1…c78d7e
Audit this contract →
← previous block
·
next block →
recent activity