pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,084,141
← previous block
next block →
recent activity
Analyzing
Block #96,084,141
9 transactions · 9 stateful · 2026-08-15 02:27:58 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,084,141
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
execFwdPositionOpsV2
#4
execFwdPositionOpsV2
#5
0x3f5c179b
#6
0x94defb17
· blocks 1
#8
setData
#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
0xb642c52c…5f4c
0x968279…9342
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0xab6bc7e0…be54
0x968279…9342
4 touches
1 conflict
0xab6bc7e0…be55
0x968279…9342
4 touches
1 conflict
0xab6bc7e0…be58
0x968279…9342
4 touches
1 conflict
0xab6bc7e0…be59
0x968279…9342
4 touches
1 conflict
0xab6bc7e0…be5a
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
0xb642c52ce9…3c5f4c
Audit this contract →
← previous block
·
next block →
recent activity