pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,287,305
← previous block
next block →
recent activity
Analyzing
Block #92,287,305
10 transactions · 9 stateful · 2026-08-01 19:35:53 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,287,305
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#5
0x0f6795d9
#6
0x6a6e4b11
#7
setData
#8
0x59558d29
#9
0xc7e3ec2c
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68caa37b…c795
0x34b655…2a6f
4 touches
1 conflict
0xa38eb2fc…1658
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0431e51f…6f91
0x34b655…2a6f
2 touches
0 conflicts
0x07d110f6…e378
0x34b655…2a6f
2 touches
0 conflicts
0x0cc8ecd2…fd22
0x34b655…2a6f
2 touches
0 conflicts
0x0dd7d6d8…3700
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
0x68caa37b30…f7c795
Audit this contract →
← previous block
·
next block →
recent activity