pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,359,944
← previous block
next block →
recent activity
Analyzing
Block #92,359,944
11 transactions · 10 stateful · 2026-08-02 01:41:11 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,359,944
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#4
0x0f6795d9
#6
0x39435dac
#7
0x6a6ea0af
#8
setData
#9
0x59558d29
· blocks 1
#5
0x0f6795d9
#10
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9f0b0dc…4827
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0bf3805f…1ce8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x3674ce56…aa52
0x34b655…2a6f
2 touches
0 conflicts
0x388633a0…86cd
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
0xb9f0b0dc52…ec4827
Audit this contract →
← previous block
·
next block →
recent activity