pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,455,709
← previous block
next block →
recent activity
Analyzing
Block #90,455,709
10 transactions · 10 stateful · 2026-07-26 09:58:45 UTC
Parallelism
60
/100
Blocked
40
%
Avg conflicts / tx
0.7
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,455,709
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execute
· blocks 3
#5
0x0f6795d9
· blocks 1
#6
0x3f5c179b
#8
setData
#9
0x39435dac
#2
execute
· blocks 2
#7
0x0f6795d9
#3
execute
· blocks 1
#4
execute
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
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeaced15b…2221
0x754704…b603
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x60f63d67…5ba0
0x34b655…2a6f
4 touches
1 conflict
0x6bf457e3…9576
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5ea9eca9…22a7
0x34b655…2a6f
2 touches
0 conflicts
0x2b9faa00…ed05
0x754704…b603
2 touches
0 conflicts
0x69550505…a0bb
0x34b655…2a6f
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:
USDC (USDC)
6 conflicts on slot
0xeaced15b26…bf2221
Audit this contract →
← previous block
·
next block →
recent activity