pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,622,233
← previous block
next block →
recent activity
Analyzing
Block #90,622,233
7 transactions · 5 stateful · 2026-07-26 23:56:28 UTC
Parallelism
71
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,622,233
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#4
0x0f6795d9
#6
setData
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b1a4848…ad1e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0x54a72bb1…1040
0x34b655…2a6f
2 touches
0 conflicts
0x5b37bb6b…aaff
0x34b655…2a6f
2 touches
0 conflicts
0x5b37bb6b…ab00
0x34b655…2a6f
2 touches
0 conflicts
0x79c5ce0d…36ed
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
0x2b1a48480d…cdad1e
Audit this contract →
← previous block
·
next block →
recent activity