pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,772,742
← previous block
next block →
recent activity
Analyzing
Block #90,772,742
10 transactions · 10 stateful · 2026-07-27 12:33:37 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,772,742
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
0x5a5d9a99
#3
0x0f6795d9
· blocks 1
#5
0x39435dac
#6
setData
#7
0x59558d29
#8
0xc7e3ec2c
#9
0xc7e3ec2c
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdc1731c…b91a
0x34b655…2a6f
4 touches
1 conflict
0x838e46c3…3cc1
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x134cc376…7c80
0x34b655…2a6f
2 touches
0 conflicts
0x171aa816…71e8
0x34b655…2a6f
2 touches
0 conflicts
0x1b8a880a…5ce4
0x34b655…2a6f
2 touches
0 conflicts
0x36ccd82a…7be7
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:
Perpl
1 conflict on slot
0xcdc1731c6b…b6b91a
Audit this contract →
← previous block
·
next block →
recent activity