pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,832,861
← previous block
next block →
recent activity
Analyzing
Block #91,832,861
10 transactions · 9 stateful · 2026-07-31 05:30:05 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,832,861
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
batchUpdate
#3
0x94defb17
· blocks 1
#5
0x57368ddf
#6
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
0x6a6c3355
#9
execOrders
#4
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9609240e…85ac
0x7b9256…1fb2
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x9609240e…85a8
0x7b9256…1fb2
4 touches
1 conflict
0x9609240e…85a9
0x7b9256…1fb2
4 touches
1 conflict
0xb7b98cd1…7fc8
0x7b9256…1fb2
3 touches
1 conflict
0xb7b98cd1…7fc9
0x7b9256…1fb2
3 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:
0x7b9256fd…e21fb2
1 conflict on slot
0x9609240e4a…8085ac
Audit this contract →
← previous block
·
next block →
recent activity