pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,858,157
← previous block
next block →
recent activity
Analyzing
Block #94,858,157
12 transactions · 11 stateful · 2026-08-10 19:25:35 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,858,157
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
#3
execFwdPositionOps
#4
0x3f5c179b
#5
0x3f5c179b
#6
0x94defb17
· blocks 1
#8
execFwdPositionOps
#9
0x6a7a2626
#10
setData
#11
execOrders
#7
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb829f78…553c
0x968279…9342
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0xcb492e7a…1fe4
0x968279…9342
4 touches
1 conflict
0xcb492e7a…1fe5
0x968279…9342
4 touches
1 conflict
0xcb492e7a…1fe7
0x968279…9342
4 touches
1 conflict
0xcb829f78…5535
0x968279…9342
4 touches
1 conflict
0xcb829f78…5536
0x968279…9342
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:
0x96827978…f09342
1 conflict on slot
0xcb829f78c2…d1553c
Audit this contract →
← previous block
·
next block →
recent activity