pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,393,500
← previous block
next block →
recent activity
Analyzing
Block #92,393,500
8 transactions · 7 stateful · 2026-08-02 04:29:56 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,393,500
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x94defb17
· blocks 2
#6
0x0f6795d9
#7
permit
#4
0x94defb17
· blocks 1
#5
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x37cb3679…71cf
0x7b9256…1fb2
6 touches
3 conflicts
0x37cb3679…71d0
0x7b9256…1fb2
6 touches
3 conflicts
0x37cb3679…71d1
0x7b9256…1fb2
6 touches
3 conflicts
0xecd097f8…2aac
0x7b9256…1fb2
6 touches
3 conflicts
0xecd097f8…2aad
0x7b9256…1fb2
6 touches
3 conflicts
0xecd097f8…2ab0
0x7b9256…1fb2
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 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:
0x7b9256fd…e21fb2
3 conflicts on slot
0x0000000000…000006
Audit this contract →
← previous block
·
next block →
recent activity