pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,493,657
← previous block
next block →
recent activity
Analyzing
Block #99,493,657
9 transactions · 9 stateful · 2026-08-27 02:17:49 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,493,657
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0x59558d29
#3
setData
#4
execFwdPositionOpsV2
· blocks 1
#5
0x94defb17
· blocks 2
#6
0x94defb17
· blocks 1
#8
execOrders
#7
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
7
w2
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd94e4cd9…b817
0x8964d7…10f8
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x9cd55081…7bdb
0x8964d7…10f8
6 touches
3 conflicts
0x9cd55081…7bdc
0x8964d7…10f8
6 touches
3 conflicts
0x9cd55081…7bdf
0x8964d7…10f8
6 touches
3 conflicts
0x9cd55081…7be0
0x8964d7…10f8
6 touches
3 conflicts
0x9cd55081…7be1
0x8964d7…10f8
6 touches
3 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:
0x8964d7c9…5b10f8
3 conflicts on slot
0xd94e4cd94f…e2b817
Audit this contract →
← previous block
·
next block →
recent activity