pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,015,055
← previous block
next block →
recent activity
Analyzing
Block #92,015,055
11 transactions · 11 stateful · 2026-07-31 20:46:38 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,015,055
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
#2
0x0f6795d9
#3
0x0f6795d9
#4
0x6a6d0a26
#5
setData
#6
0x39435dac
· blocks 1
#8
0x59558d29
#9
0xc7e3ec2c
#10
0xc7e3ec2c
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa51de3df…c65a
0x34b655…2a6f
4 touches
1 conflict
0x81469fc5…c575
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x96b35b79…54f4
0x34b655…2a6f
4 touches
1 conflict
0x313fa00e…b47f
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e65
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e66
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
0xa51de3dfe9…dec65a
Audit this contract →
← previous block
·
next block →
recent activity