pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,016,934
← previous block
next block →
recent activity
Analyzing
Block #96,016,934
9 transactions · 8 stateful · 2026-08-14 20:49:54 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,016,934
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x4d8dc985
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x94defb17
· blocks 1
#7
setData
#8
0x39435dac
#5
0x94defb17
#6
0xcffefd2e
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcef96a4a…f984
0x968279…9342
4 touches
1 conflict
0xcef96a4a…f987
0x968279…9342
4 touches
1 conflict
0xcef96a4a…f988
0x968279…9342
4 touches
1 conflict
0xcef96a4a…f98a
0x968279…9342
4 touches
1 conflict
0xb9a63764…f004
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
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
0xcef96a4a32…78f984
Audit this contract →
← previous block
·
next block →
recent activity