pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,113,948
← previous block
next block →
recent activity
Analyzing
Block #99,113,948
13 transactions · 12 stateful · 2026-08-25 18:26:33 UTC
Parallelism
85
/100
Blocked
25
%
Avg conflicts / tx
0.23
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,113,948
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execute302
#3
0xab083028
· blocks 1
#5
execOrders
· blocks 1
#6
0x59558d29
#8
setData
#9
0x3f5c179b
#10
forward
· blocks 1
#12
execOrders
#4
0xab083028
#7
execFwdPositionOpsV2
#11
forward
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
7
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000b
0x68ba3f…6e5e
4 touches
1 conflict
0x152f8e3d…3da0
0x34b655…2a6f
4 touches
1 conflict
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0xe912f452…7e42
0x6f4756…dd5b
2 touches
0 conflicts
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:
0x68ba3f3b…f96e5e
1 conflict on slot
0x0000000000…00000b
Audit this contract →
← previous block
·
next block →
recent activity