pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,016,943
← previous block
next block →
recent activity
Analyzing
Block #96,016,943
11 transactions · 8 stateful · 2026-08-14 20:49:57 UTC
Parallelism
82
/100
Blocked
25
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,016,943
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#2
updatePrices
#3
0x5acec890
#4
0xcffefd2e
· blocks 1
#5
updateDataFeedsValuesPartial
#7
forward
#9
setData
#10
0x61d59c2d
#6
0xcffefd2e
#8
0xcffefd2e
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
6
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb9a63764…f004
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x18e86f02…fa98
0x34b655…2a6f
2 touches
0 conflicts
0x42522e76…2592
0x34b655…2a6f
2 touches
0 conflicts
0x5d3bb355…4549
0x34b655…2a6f
2 touches
0 conflicts
0x6d1b72ee…6b77
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:
Perpl
1 conflict on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity