pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,300,072
← previous block
next block →
recent activity
Analyzing
Block #90,300,072
10 transactions · 8 stateful · 2026-07-25 20:42:42 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,300,072
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
0x5a5d9a99
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
executeBatch
#7
setData
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16dcea2f…25e6
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfcb5df9b…b874
0x34b655…2a6f
4 touches
1 conflict
0xbe6ecaa0…de0f
0x34b655…2a6f
4 touches
1 conflict
0x1321736a…43e3
0x34b655…2a6f
2 touches
0 conflicts
0x155e52ca…fac7
0x34b655…2a6f
2 touches
0 conflicts
0x155f3b9a…4b9f
0x34b655…2a6f
2 touches
0 conflicts
0x226ae29a…2612
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
0x16dcea2fe5…b525e6
Audit this contract →
← previous block
·
next block →
recent activity