pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,441,346
← previous block
next block →
recent activity
Analyzing
Block #90,441,346
7 transactions · 7 stateful · 2026-07-26 08:46:15 UTC
Parallelism
29
/100
Blocked
57
%
Avg conflicts / tx
1.43
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,441,346
· 7 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
execFwdPositionOps
· blocks 4
#6
setData
#2
execFwdPositionOps
· blocks 3
#3
execFwdPositionOps
· blocks 2
#4
execFwdPositionOps
· blocks 1
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
5
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb9ccd689…c424
0x34b655…2a6f
8 touches
6 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
8 touches
6 conflicts
0x28cde80e…b851
0x34b655…2a6f
4 touches
1 conflict
0x349f436e…80e6
0x34b655…2a6f
4 touches
1 conflict
0x38badd90…a68c
0x34b655…2a6f
4 touches
1 conflict
0x3f57bd36…7796
0x34b655…2a6f
4 touches
1 conflict
0x5b9528ae…c472
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:
Perpl
6 conflicts on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity