pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#90,208,230
← previous block
next block →
recent activity
Analyzing
Block #90,208,230
10 transactions · 10 stateful · 2026-07-25 12:58:38 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,208,230
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#4
executeBatch
· blocks 1
#7
0x6a64b375
#8
setData
#9
0xc7e3ec2c
#5
executeBatch
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fb9e50c…1a35
0x34b655…2a6f
4 touches
1 conflict
0x3a0901d8…c944
0x34b655…2a6f
4 touches
1 conflict
0x3e3f27ce…580c
0x34b655…2a6f
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x628359b1…7263
0x34b655…2a6f
4 touches
1 conflict
0x78255c70…2733
0x34b655…2a6f
4 touches
1 conflict
0x78255c70…2734
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
0x0fb9e50cd4…5a1a35
Audit this contract →
← previous block
·
next block →
recent activity