pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,229,636
← previous block
next block →
recent activity
Analyzing
Block #94,229,636
10 transactions · 8 stateful · 2026-08-08 14:31:11 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,229,636
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 2
#5
forward
#7
0xed82b078
#8
0x6a773e27
#9
setData
#4
0x0f6795d9
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf63c2a2b…bc60
0x34b655…2a6f
4 touches
1 conflict
0x272e5bd6…252d
0x34b655…2a6f
4 touches
1 conflict
0x4ac4de26…a5c8
0x34b655…2a6f
4 touches
1 conflict
0x4f1ad4b4…e00a
0x34b655…2a6f
4 touches
1 conflict
0x513b0c80…d2d9
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
0xf63c2a2b51…78bc60
Audit this contract →
← previous block
·
next block →
recent activity