pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,160,488
← previous block
next block →
recent activity
Analyzing
Block #99,160,488
23 transactions · 16 stateful · 2026-08-25 22:20:47 UTC
Parallelism
91
/100
Blocked
19
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,160,488
· 23 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa9b28aa6
· blocks 2
#2
0xd524a9da
#4
matchOrders
#5
0x513fe4…d014
#7
0x59558d29
#8
execPerpOps
· blocks 1
#10
0xb414539a
#11
execPerpOps
#12
execPerpOps
#13
0xe3a3c9cc
#14
setData
#15
0x62be7533
#16
execFwdPositionOpsV2
#17
0x3f5c179b
#18
0x3f5c179b
#19
0x0c7abd22
#20
execOrders
#21
commit
#22
withdraw
#3
exactInputSingle
#6
0xab083028
#9
execPerpOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
6
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0002
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x37df7523…ccbb
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
0xea02471df2…601539
Audit this contract →
← previous block
·
next block →
recent activity