pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,887,216
← previous block
next block →
recent activity
Analyzing
Block #90,887,216
9 transactions · 9 stateful · 2026-07-27 22:09:39 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,887,216
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x532c46db
· blocks 2
#5
0xc5a04723
#6
0x0f6795d9
#7
0x0f6795d9
#8
setData
#3
0x532c46db
· blocks 1
#4
0x532c46db
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x944a7d7b…7003
0x851145…3f07
6 touches
3 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
6 touches
3 conflicts
0x11b69a7e…334e
0x01bff4…1071
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x3352fed8…8092
0x01bff4…1071
2 touches
0 conflicts
0x5261f6ab…9aa1
0x01bff4…1071
2 touches
0 conflicts
0x3040553c…5e28
0x754704…b603
2 touches
0 conflicts
0x3d9eb674…b3fb
0x754704…b603
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:
0x851145ea…9f3f07
3 conflicts on slot
0x944a7d7b3a…7e7003
Audit this contract →
← previous block
·
next block →
recent activity