pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,824,882
← previous block
next block →
recent activity
Analyzing
Block #90,824,882
9 transactions · 7 stateful · 2026-07-27 16:56:03 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,824,882
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 1
#3
0x0f6795d9
· blocks 1
#6
0x39435dac
#7
0x6a678e1b
#8
setData
#4
0x0f6795d9
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfefd9ff3…81b2
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xf726e2e2…e561
0x34b655…2a6f
4 touches
1 conflict
0xf7f6893b…7d2f
0x34b655…2a6f
4 touches
1 conflict
0x0424d4ef…54fb
0x34b655…2a6f
4 touches
1 conflict
0x0c15f714…46ab
0x34b655…2a6f
4 touches
1 conflict
0x1c3295fd…097a
0x34b655…2a6f
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
0xfefd9ff392…8e81b2
Audit this contract →
← previous block
·
next block →
recent activity