pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,802,548
← previous block
next block →
recent activity
Analyzing
Block #90,802,548
7 transactions · 7 stateful · 2026-07-27 15:03:37 UTC
Parallelism
57
/100
Blocked
29
%
Avg conflicts / tx
0.57
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,802,548
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 2
#4
0x6a6773c0
#5
0x39435dac
· blocks 1
#3
0x0f6795d9
· blocks 1
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xabd0bcfc…64e2
0x34b655…2a6f
6 touches
3 conflicts
0x6af3bfab…17a8
0x34b655…2a6f
4 touches
1 conflict
0x742436a7…c4d4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0494220d…abf7
0x34b655…2a6f
2 touches
0 conflicts
0x1041bcb3…4c7a
0x34b655…2a6f
2 touches
0 conflicts
0x1321736a…43e3
0x34b655…2a6f
2 touches
0 conflicts
0x364289f7…f98a
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
3 conflicts on slot
0xabd0bcfc80…a364e2
Audit this contract →
← previous block
·
next block →
recent activity