pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#90,526,102
← previous block
next block →
recent activity
Analyzing
Block #90,526,102
8 transactions · 6 stateful · 2026-07-26 15:52:53 UTC
Parallelism
75
/100
Blocked
33
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,526,102
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x0f6795d9
· blocks 2
#4
updateDataFeedsValuesPartial
#6
0x39435dac
#7
setData
#3
0x0f6795d9
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71e46a24…2cb4
0x34b655…2a6f
4 touches
1 conflict
0x8329c51e…4064
0x34b655…2a6f
4 touches
1 conflict
0x8329c51e…4065
0x34b655…2a6f
4 touches
1 conflict
0xba00d7e1…1878
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x06f3ed5a…b2e5
0x34b655…2a6f
4 touches
1 conflict
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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
0x71e46a2497…562cb4
Audit this contract →
← previous block
·
next block →
recent activity