pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,395,780
← previous block
next block →
recent activity
Analyzing
Block #90,395,780
8 transactions · 8 stateful · 2026-07-26 04:52:07 UTC
Parallelism
50
/100
Blocked
38
%
Avg conflicts / tx
0.5
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,395,780
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x5a5d9a99
· blocks 2
#2
updateDataFeedsValuesPartial
#6
setData
#7
0x39435dac
#3
0x0f6795d9
· blocks 1
#4
0x0f6795d9
· blocks 1
#5
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94bb14fe…8f47
0x34b655…2a6f
6 touches
3 conflicts
0xbeae9d45…61ce
0x34b655…2a6f
6 touches
3 conflicts
0x147c952c…b00d
0x34b655…2a6f
4 touches
1 conflict
0x1d8d5450…9db6
0x34b655…2a6f
4 touches
1 conflict
0x2d3930d3…c9b8
0x34b655…2a6f
4 touches
1 conflict
0x342222e8…2ec4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5ea9eca9…22a6
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
3 conflicts on slot
0x94bb14fe40…668f47
Audit this contract →
← previous block
·
next block →
recent activity