pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,483,092
← previous block
next block →
recent activity
Analyzing
Block #90,483,092
9 transactions · 9 stateful · 2026-07-26 12:16:34 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,483,092
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
execFwdPositionOps
· blocks 1
#3
0x3f5c179b
#4
execFwdPositionOps
#5
handleOps
#7
0x6a65fb19
#8
setData
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfc24540b…6463
0x34b655…2a6f
4 touches
1 conflict
0x0f32c4d1…40e7
0x34b655…2a6f
2 touches
0 conflicts
0x199b58a5…9811
0x34b655…2a6f
2 touches
0 conflicts
0x236dd751…aa8a
0x34b655…2a6f
2 touches
0 conflicts
0x236dd751…aa8b
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e65
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
0x2d071de0f2…94c86e
Audit this contract →
← previous block
·
next block →
recent activity