pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,524,363
← previous block
next block →
recent activity
Analyzing
Block #95,524,363
9 transactions · 8 stateful · 2026-08-13 03:30:53 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,524,363
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
executeBatch
#6
0x3f5c179b
#7
0x0f6795d9
#8
setData
#2
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xc3feb544…02db
0x34b655…2a6f
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0712100b…e8bc
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x326a02b5…8dad
0x34b655…2a6f
2 touches
0 conflicts
0x61bbc5e4…67a2
0x34b655…2a6f
2 touches
0 conflicts
0x694d5d59…4621
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
0x7de579746e…f0f5ba
Audit this contract →
← previous block
·
next block →
recent activity