pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,891,538
← previous block
next block →
recent activity
Analyzing
Block #90,891,538
11 transactions · 10 stateful · 2026-07-27 22:31:24 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,891,538
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x0f6795d9
#3
0x0f6795d9
· blocks 1
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
0x3f5c179b
#8
transfer
#9
setData
#10
0x39435dac
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x05b1b07a…7a99
0x34b655…2a6f
2 touches
0 conflicts
0x0bd95eb4…e562
0x34b655…2a6f
2 touches
0 conflicts
0x167de262…f61f
0x34b655…2a6f
2 touches
0 conflicts
0x286ff32c…2782
0x34b655…2a6f
2 touches
0 conflicts
0x2acd1d70…19ed
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
0xe4af4c87c3…c59964
Audit this contract →
← previous block
·
next block →
recent activity