pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,458,819
← previous block
next block →
recent activity
Analyzing
Block #90,458,819
9 transactions · 8 stateful · 2026-07-26 10:14:24 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,458,819
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x0f6795d9
· blocks 1
#4
0x0f6795d9
#5
forward
#6
0x39435dac
#7
setData
#8
0xc7e3ec2c
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4268cc8…dc39
0x34b655…2a6f
4 touches
1 conflict
0xc3412055…65dd
0x34b655…2a6f
4 touches
1 conflict
0xc3412055…65de
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcb54cde8…5f6e
0x34b655…2a6f
4 touches
1 conflict
0xf1f91cb6…3428
0x34b655…2a6f
4 touches
1 conflict
0x09a90ed3…6897
0x34b655…2a6f
4 touches
1 conflict
0x0f07cfaf…9a8a
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
1 conflict on slot
0xf4268cc8b9…24dc39
Audit this contract →
← previous block
·
next block →
recent activity