pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,849,883
← previous block
next block →
recent activity
Analyzing
Block #94,849,883
9 transactions · 9 stateful · 2026-08-10 18:43:58 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,849,883
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x5acec890
#3
execOrders
#4
execFwdPositionOps
· blocks 1
#5
0x94defb17
· blocks 1
#8
setData
#6
0x94defb17
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0655dcb…2016
0x968279…9342
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x7e52bfe2…11f4
0x968279…9342
4 touches
1 conflict
0x7e52bfe2…11f5
0x968279…9342
4 touches
1 conflict
0x7e52bfe2…11f8
0x968279…9342
4 touches
1 conflict
0x7e52bfe2…11f9
0x968279…9342
4 touches
1 conflict
0xa0655dcb…2013
0x968279…9342
4 touches
1 conflict
0xa0655dcb…2014
0x968279…9342
4 touches
1 conflict
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:
0x96827978…f09342
1 conflict on slot
0xa0655dcb3c…302016
Audit this contract →
← previous block
·
next block →
recent activity