pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#91,157,928
← previous block
next block →
recent activity
Analyzing
Block #91,157,928
10 transactions · 10 stateful · 2026-07-28 20:52:27 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,157,928
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5a5d9a99
#3
0x0f6795d9
· blocks 1
#4
0x0f6795d9
#6
approve
#7
setData
#8
0x39435dac
#9
0xc7e3ec2c
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f394483…ff62
0x34b655…2a6f
4 touches
1 conflict
0x62b26c37…87d6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcd26fba5…21c6
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc683bfb0…3bbc
0x34b655…2a6f
4 touches
1 conflict
0x11bff529…179a
0x34b655…2a6f
3 touches
1 conflict
0xda65cebb…3038
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
0x4f39448303…4fff62
Audit this contract →
← previous block
·
next block →
recent activity