pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,535,963
← previous block
next block →
recent activity
Analyzing
Block #98,535,963
9 transactions · 9 stateful · 2026-08-23 17:22:44 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,535,963
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
execOrders
· blocks 1
#3
0x59558d29
#5
closeBetting
#6
setData
#7
execOrders
· blocks 1
#4
execFwdPositionOpsV2
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1408e7c7…f324
0x34b655…2a6f
4 touches
1 conflict
0x5d6da397…6c5c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00d67843…2809
0x34b655…2a6f
2 touches
0 conflicts
0x07487c88…d403
0x34b655…2a6f
2 touches
0 conflicts
0x1398e9f0…69ac
0x34b655…2a6f
2 touches
0 conflicts
0x19e22068…53e9
0x34b655…2a6f
2 touches
0 conflicts
0x3a874400…e10d
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:
Perpl
1 conflict on slot
0x1408e7c773…87f324
Audit this contract →
← previous block
·
next block →
recent activity