pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,888,127
← previous block
next block →
recent activity
Analyzing
Block #90,888,127
11 transactions · 10 stateful · 2026-07-27 22:14:14 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,888,127
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
0x4d8dc985
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#6
0x39435dac
#7
setData
#8
0x39435dac
· blocks 1
#10
0xc7e3ec2c
#5
0xed82b078
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8046ca3c…f094
0x34b655…2a6f
4 touches
1 conflict
0x8b46e9d1…e148
0x34b655…2a6f
4 touches
1 conflict
0x25329a48…4e00
0x34b655…2a6f
4 touches
1 conflict
0xa13e2069…6171
0x34b655…2a6f
4 touches
1 conflict
0xc864e93d…8111
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf4ddd32b…cc5a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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
0x8046ca3cb2…45f094
Audit this contract →
← previous block
·
next block →
recent activity