pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,696,968
← previous block
next block →
recent activity
Analyzing
Block #90,696,968
8 transactions · 8 stateful · 2026-07-27 06:12:27 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,696,968
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
execFwdPositionOps
· blocks 1
#4
batchUpdate
#5
execFwdPositionOps
#7
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x33a0506d…30de
0x34b655…2a6f
4 touches
1 conflict
0xd6c0349d…05b0
0x34b655…2a6f
4 touches
1 conflict
0x33ff1f18…7f25
0x065c9d…c394
2 touches
0 conflicts
0x6a833e4a…90e3
0x065c9d…c394
2 touches
0 conflicts
0xc34244b1…bb0c
0x065c9d…c394
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity