pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,855,278
← previous block
next block →
recent activity
Analyzing
Block #93,855,278
10 transactions · 10 stateful · 2026-08-07 07:03:38 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,855,278
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0x5acec890
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x29eed2d3
· blocks 1
#8
0x6a7583c2
#9
setData
#3
0x5acec890
#7
0x29eed2d3
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0xc82f19fb…da76
0x928dc8…8207
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x09cac653…86ba
0x34b655…2a6f
2 touches
0 conflicts
0x124a2fe8…2ea9
0x34b655…2a6f
2 touches
0 conflicts
0x19bb5bdd…89d7
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x4a1a64d1…3771
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:
USDC (USDC)
1 conflict on slot
0x5311f86450…380984
Audit this contract →
← previous block
·
next block →
recent activity