pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,534,931
← previous block
next block →
recent activity
Analyzing
Block #90,534,931
10 transactions · 9 stateful · 2026-07-26 16:37:18 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,534,931
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a663835
#2
0x5a5d9a99
· blocks 2
#4
0x3f5c179b
#5
0x5339c59f
#6
0x0f6795d9
#7
0x0f6795d9
#8
setData
#3
0x0f6795d9
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xec152baf…a069
0x34b655…2a6f
4 touches
1 conflict
0x94ddea60…a24d
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x0ac36fc5…e4e6
0x34b655…2a6f
2 touches
0 conflicts
0x366748e9…1282
0x34b655…2a6f
2 touches
0 conflicts
0x3ba887f3…b67c
0x34b655…2a6f
2 touches
0 conflicts
0x55cf4758…265c
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
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity