pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,681,177
← previous block
next block →
recent activity
Analyzing
Block #90,681,177
6 transactions · 5 stateful · 2026-07-27 04:53:01 UTC
Parallelism
67
/100
Blocked
40
%
Avg conflicts / tx
0.33
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,681,177
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 1
#4
0x39435dac
· blocks 1
#3
0x0f6795d9
#5
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2099241a…2d2a
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x042a8476…b4f1
0x34b655…2a6f
2 touches
0 conflicts
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x0a005879…de60
0x34b655…2a6f
2 touches
0 conflicts
0x278686dc…698d
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e65
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
0x2099241a67…ad2d2a
Audit this contract →
← previous block
·
next block →
recent activity