pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,655,918
← previous block
next block →
recent activity
Analyzing
Block #95,655,918
11 transactions · 9 stateful · 2026-08-13 14:32:35 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,655,918
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0xb2d4797b
· blocks 2
#5
updateDataFeedsValuesPartial
#6
execOrders
#7
execFwdPositionOps
#8
0x94defb17
#9
execFwdPositionOps
#10
setData
#3
0xb2d4797b
· blocks 1
#4
0xb2d4797b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0031
0x59df86…2780
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x4a5fdab0…542a
0x065c9d…c394
2 touches
0 conflicts
0x7b3f7945…95cf
0x065c9d…c394
2 touches
0 conflicts
0xb33ff823…1188
0x065c9d…c394
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
3 conflicts on slot
0x0000000000…000031
Audit this contract →
← previous block
·
next block →
recent activity