pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,228,217
← previous block
next block →
recent activity
Analyzing
Block #94,228,217
9 transactions · 8 stateful · 2026-08-08 14:23:58 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,228,217
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
#2
0x0f6795d9
· blocks 1
#5
forward
#6
updateDataFeedsValuesPartial
#7
0x6a773c76
#8
setData
#3
0x0f6795d9
· blocks 1
#4
0x0f6795d9
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
0xa887a224…03d1
0x34b655…2a6f
4 touches
1 conflict
0x5534258c…665f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf28d07b9…4fb2
0x34b655…2a6f
4 touches
1 conflict
0x40aafdd2…46da
0x34b655…2a6f
2 touches
0 conflicts
0x59eabcdc…e01d
0x34b655…2a6f
2 touches
0 conflicts
0x7103aaf4…ddc5
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
0xa887a2247a…4b03d1
Audit this contract →
← previous block
·
next block →
recent activity