pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,810,262
← previous block
next block →
recent activity
Analyzing
Block #90,810,262
10 transactions · 10 stateful · 2026-07-27 15:42:27 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,810,262
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0x5a5d9a99
#3
0x0f6795d9
#4
0x3f5c179b
#5
0x39435dac
· blocks 1
#7
0x6a677cdb
#8
setData
#9
0x39435dac
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b47245e…a342
0x34b655…2a6f
4 touches
1 conflict
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0x86629ec1…7569
0x34b655…2a6f
3 touches
1 conflict
0x07b86c51…cdae
0x2a68ba…90c5
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0xf7640726…19a2
0x2a68ba…90c5
2 touches
0 conflicts
0x08d53462…97ef
0x2b46c0…1669
2 touches
0 conflicts
0x39977254…07b1
0x2b46c0…1669
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
0x6b47245e5d…eda342
Audit this contract →
← previous block
·
next block →
recent activity