pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,025,760
← previous block
next block →
recent activity
Analyzing
Block #96,025,760
9 transactions · 7 stateful · 2026-08-14 21:34:18 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,025,760
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5acec890
#3
0x5acec890
#4
0x5acec890
· blocks 1
#6
0x3f5c179b
#7
0xcffefd2e
#8
setData
#5
0xcffefd2e
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fab7fbe…1ce5
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00a4b314…7160
0x34b655…2a6f
2 touches
0 conflicts
0x0fd1ecf0…ee41
0x34b655…2a6f
2 touches
0 conflicts
0x124a2fe8…2ea9
0x34b655…2a6f
2 touches
0 conflicts
0x20daa8c4…f72a
0x34b655…2a6f
2 touches
0 conflicts
0x2c8f52ce…fe9a
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
0x5fab7fbe22…391ce5
Audit this contract →
← previous block
·
next block →
recent activity