pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,018,801
← previous block
next block →
recent activity
Analyzing
Block #91,018,801
5 transactions · 4 stateful · 2026-07-28 09:12:25 UTC
Parallelism
60
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,018,801
· 5 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 1
#4
setData
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0cd89b3c…836c
0x34b655…2a6f
4 touches
1 conflict
0x3cb7ee74…b8a5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x88e771e8…7d4a
0x34b655…2a6f
4 touches
1 conflict
0xea559e7b…41f4
0x34b655…2a6f
4 touches
1 conflict
0x145b9bbf…e50f
0x34b655…2a6f
2 touches
0 conflicts
0x15eb6170…3da3
0x34b655…2a6f
2 touches
0 conflicts
0x177f8108…ff11
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
0x0cd89b3c30…af836c
Audit this contract →
← previous block
·
next block →
recent activity