pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,944,968
← previous block
next block →
recent activity
Analyzing
Block #90,944,968
9 transactions · 6 stateful · 2026-07-28 03:00:10 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,944,968
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x4d8dc985
· blocks 1
#2
0x4d8dc985
#3
updateDataFeedsValuesPartial
#4
0x57368ddf
#6
0x0f6795d9
#7
0x6a681bb2
#8
setData
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6eae156…f526
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x3bdd71a2…b6eb
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
2 touches
0 conflicts
0xbdc80bf7…e947
0x34b655…2a6f
2 touches
0 conflicts
0xd66696e0…0842
0x34b655…2a6f
2 touches
0 conflicts
0xeaea4469…be89
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
0xc6eae15637…cef526
Audit this contract →
← previous block
·
next block →
recent activity