pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,945,303
← previous block
next block →
recent activity
Analyzing
Block #90,945,303
8 transactions · 8 stateful · 2026-07-28 03:01:52 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,945,303
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
0x5a5d9a99
#3
0x0f6795d9
#4
executeBatch
#6
updateDataFeedsValuesPartial
#7
setData
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0f3152e8…f181
0x34b655…2a6f
2 touches
0 conflicts
0x17aad0b2…59d0
0x34b655…2a6f
2 touches
0 conflicts
0x19d0122b…937c
0x34b655…2a6f
2 touches
0 conflicts
0x25329a48…4e00
0x34b655…2a6f
2 touches
0 conflicts
0x25e0ba32…ca5c
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
0x4acbdbcf7f…d0a8c6
Audit this contract →
← previous block
·
next block →
recent activity