pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#91,011,890
← previous block
next block →
recent activity
Analyzing
Block #91,011,890
11 transactions · 10 stateful · 2026-07-28 08:37:37 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
#91,011,890
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
· blocks 2
#3
0x4d8dc985
#4
0x0f6795d9
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#8
0x94defb17
#9
0x6a686ac9
#10
setData
#2
0xab083028
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa68ec550…9a05
0x851145…3f07
4 touches
1 conflict
0x2a628ea8…5918
0x851145…3f07
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1b6c23a0…723b
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xd1c9123c…1d08
0x851145…3f07
3 touches
1 conflict
0xb5e62ebc…728c
0x851145…3f07
3 touches
1 conflict
0x7a12283f…b18a
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
0xa68ec550eb…ae9a05
Audit this contract →
← previous block
·
next block →
recent activity