pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,077,756
← previous block
next block →
recent activity
Analyzing
Block #98,077,756
12 transactions · 12 stateful · 2026-08-22 02:49:29 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
#98,077,756
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe33905c2
#2
matchOrders
· blocks 1
#4
execOrders
· blocks 1
#5
0x6ad2e98b
#6
0xab083028
#7
0xb2d4797b
#8
0x59558d29
#10
forward
#11
transferWithAuthorization
#3
matchOrders
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x52bbc0a2…2b5b
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x30d3b573…4288
0x34b655…2a6f
4 touches
1 conflict
0x3129b531…9db1
0x754704…b603
4 touches
1 conflict
0x64b004ab…60af
0x754704…b603
4 touches
1 conflict
0xba68e65e…c29a
0x754704…b603
4 touches
1 conflict
0x823c5bec…e738
0x99c7a7…8bf0
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:
Perpl
1 conflict on slot
0x326a02b5c5…5c8dad
Audit this contract →
← previous block
·
next block →
recent activity