pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,878,725
← previous block
next block →
recent activity
Analyzing
Block #99,878,725
13 transactions · 13 stateful · 2026-08-28 10:49:17 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,878,725
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updatePrices
#3
0x5acec890
#4
0x5acec890
#5
0x5acec890
#6
0x59558d29
#7
transferWithAuthorization
#8
setData
#9
0xed82b078
#10
transfer
#11
execOrders
· blocks 1
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0f5d668…99ac
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x825f9b19…8669
0x34b655…2a6f
3 touches
1 conflict
0x1d1eb3d2…d573
0x34b655…2a6f
3 touches
1 conflict
0xecd87a39…d9c5
0x34b655…2a6f
2 touches
0 conflicts
0x15c6ded9…48e7
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
0xb0f5d66855…1a99ac
Audit this contract →
← previous block
·
next block →
recent activity