pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,076,578
← previous block
next block →
recent activity
Analyzing
Block #99,076,578
13 transactions · 11 stateful · 2026-08-25 15:18:13 UTC
Parallelism
85
/100
Blocked
18
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,076,578
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0x5acec890
· blocks 1
#3
0xab083028
· blocks 1
#4
execOrders
#5
execOrder
#6
0x59558d29
#7
execOrders
#9
setData
#10
0xb8c601…4550
#11
0x4a6c15…07e3
#8
0xed82b078
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
8
w1
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x03a6363b…ad2b
0x34b655…2a6f
2 touches
0 conflicts
0x1988193b…6241
0x34b655…2a6f
2 touches
0 conflicts
0x3b29b153…d0f4
0x34b655…2a6f
2 touches
0 conflicts
0x52df67cf…f77b
0x34b655…2a6f
2 touches
0 conflicts
0x62910921…3016
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
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity