pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,124,941
← previous block
next block →
recent activity
Analyzing
Block #96,124,941
9 transactions · 8 stateful · 2026-08-15 05:53:10 UTC
Parallelism
56
/100
Blocked
38
%
Avg conflicts / tx
0.67
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,124,941
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOpsV2
#3
execFwdPositionOpsV2
#4
0xb2d4797b
· blocks 3
#8
0x3f5c179b
#5
0xb2d4797b
· blocks 2
#6
0xb2d4797b
· blocks 1
#7
0xb2d4797b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0031
0x59df86…2780
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05896939…9f49
0x34b655…2a6f
2 touches
0 conflicts
0x101db199…8fb0
0x34b655…2a6f
2 touches
0 conflicts
0x168f7615…a8de
0x34b655…2a6f
2 touches
0 conflicts
0x1953dd4a…340b
0x34b655…2a6f
2 touches
0 conflicts
0x2021fb2a…d63b
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:
0x59df8637…6d2780
6 conflicts on slot
0x0000000000…000031
Audit this contract →
← previous block
·
next block →
recent activity