pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,240,321
← previous block
next block →
recent activity
Analyzing
Block #90,240,321
8 transactions · 7 stateful · 2026-07-25 15:40:25 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,240,321
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x0f6795d9
· blocks 1
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x39435dac
#7
0xc7e3ec2c
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x750fb05c…0e99
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xd9c216f4…3fd6
0x34b655…2a6f
4 touches
1 conflict
0x6bf28622…3014
0x34b655…2a6f
4 touches
1 conflict
0x87ab06cc…147e
0x34b655…2a6f
3 touches
1 conflict
0x38d4befd…1572
0x34b655…2a6f
2 touches
0 conflicts
0x3d158563…8713
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
0x750fb05c31…040e99
Audit this contract →
← previous block
·
next block →
recent activity