pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,512,512
← previous block
next block →
recent activity
Analyzing
Block #90,512,512
8 transactions · 7 stateful · 2026-07-26 14:44:32 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,512,512
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5a5d9a99
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#6
0x6a661dc8
#7
setData
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf61165ef…adb9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x24e3bf88…17bf
0x34b655…2a6f
4 touches
1 conflict
0x32646adf…e05d
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7c51d9aa…af39
0x34b655…2a6f
4 touches
1 conflict
0x7e1d87b8…291c
0x34b655…2a6f
4 touches
1 conflict
0x85c84f98…06d7
0x34b655…2a6f
4 touches
1 conflict
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
0xf61165ef5e…3badb9
Audit this contract →
← previous block
·
next block →
recent activity