pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,326,397
← previous block
next block →
recent activity
Analyzing
Block #92,326,397
12 transactions · 10 stateful · 2026-08-01 22:52:29 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,326,397
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5acec890
#3
0x5acec890
#4
0x39435dac
#5
0x0f6795d9
#6
0x0f6795d9
· blocks 1
#8
updateDataFeedsValuesPartial
#9
0x6a6e7925
#10
setData
#11
0x39435dac
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc7d5199…c05f
0x34b655…2a6f
4 touches
1 conflict
0xe1af7d74…7621
0x34b655…2a6f
4 touches
1 conflict
0xe1af7d74…7622
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xaf1f7317…b925
0x34b655…2a6f
3 touches
1 conflict
0x0db73805…8212
0x34b655…2a6f
2 touches
0 conflicts
0x355a120e…d7c2
0x34b655…2a6f
2 touches
0 conflicts
0x41e2ea73…ddf8
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
0xbc7d519930…72c05f
Audit this contract →
← previous block
·
next block →
recent activity