pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#89,680,809
← previous block
next block →
recent activity
Analyzing
Block #89,680,809
10 transactions · 10 stateful · 2026-07-23 16:37:28 UTC
Parallelism
80
/100
Blocked
30
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,680,809
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xd60faa87
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 2
#5
0x39435dac
#7
0x6a6243c0
#8
setData
#2
swapWithBackendSignature
#6
0x0f6795d9
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
6
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaeabffea…5dd4
0x0a3323…0a3c
4 touches
1 conflict
0x00000000…0001
0x04ddf6…7f33
4 touches
1 conflict
0x00000000…0003
0x04ddf6…7f33
4 touches
1 conflict
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0xb7e4c78a…f3f6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0x04ddf6…7f33
4 touches
1 conflict
0x6901bef4…4a69
0x754704…b603
4 touches
1 conflict
0x09000000…0001
0x000000…1000
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:
0x0a332311…6e0a3c
1 conflict on slot
0xaeabffeafa…9e5dd4
Audit this contract →
← previous block
·
next block →
recent activity