pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,559,088
← previous block
next block →
recent activity
Analyzing
Block #92,559,088
12 transactions · 11 stateful · 2026-08-02 18:22:44 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,559,088
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xa96df62f
#3
0x5acec890
#4
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#7
callDiamondWithPermit2
#8
0x3f5c179b
#9
0x94defb17
· blocks 1
#11
setData
#5
execFwdPositionOps
#10
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9996fe41…07b6
0x968279…9342
4 touches
1 conflict
0x4069a820…eec3
0x968279…9342
4 touches
1 conflict
0x4069a820…eec6
0x968279…9342
4 touches
1 conflict
0x4069a820…eec7
0x968279…9342
4 touches
1 conflict
0x4069a820…eec8
0x968279…9342
4 touches
1 conflict
0x9996fe41…07b3
0x968279…9342
4 touches
1 conflict
0x9996fe41…07b4
0x968279…9342
4 touches
1 conflict
0x4fe65078…76b9
0x34b655…2a6f
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
0x9996fe41b2…ef07b6
Audit this contract →
← previous block
·
next block →
recent activity