pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#91,026,025
← previous block
next block →
recent activity
Analyzing
Block #91,026,025
9 transactions · 8 stateful · 2026-07-28 09:48:47 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,026,025
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x57368ddf
#3
0x0f6795d9
· blocks 2
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#4
0x0f6795d9
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x145b9bbf…e50e
0x34b655…2a6f
4 touches
1 conflict
0x86a2e799…7474
0x34b655…2a6f
4 touches
1 conflict
0x145b9bbf…e50f
0x34b655…2a6f
4 touches
1 conflict
0x901f4dfc…1ba4
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xcf090a80…4536
0x34b655…2a6f
4 touches
1 conflict
0x15eb6170…3da3
0x34b655…2a6f
4 touches
1 conflict
0x194be77e…58ae
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
1 conflict on slot
0x145b9bbfee…a5e50e
Audit this contract →
← previous block
·
next block →
recent activity