pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,396,576
← previous block
next block →
recent activity
Analyzing
Block #95,396,576
10 transactions · 10 stateful · 2026-08-12 16:47:20 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,396,576
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
· blocks 1
#2
0x3f5c179b
#4
0x0f6795d9
#5
updateDataFeedsValuesPartial
#6
approve
#7
setData
#8
0x59558d29
#9
0x39435dac
#3
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x0bc80bb4…a97c
0x851145…3f07
4 touches
1 conflict
0x1ea0a6bc…6a74
0x2a68ba…90c5
4 touches
1 conflict
0xc0364fa8…181e
0x851145…3f07
4 touches
1 conflict
0xfd94e24a…9278
0x851145…3f07
4 touches
1 conflict
0x0890732f…31e3
0x851145…3f07
3 touches
1 conflict
0x5a409e7f…09b6
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…1867
0x2b46c0…1669
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:
0x851145ea…9f3f07
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity