pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,201,574
← previous block
next block →
recent activity
Analyzing
Block #75,201,574
11 transactions · 9 stateful · 2026-05-17 14:33:53 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,201,574
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
forward
#6
0x6df9e92b
· blocks 1
#8
0x6a09d249
#9
setData
#10
0xbb383a…8f7c
#2
execute
#7
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67813250…9467
0xb744f5…7777
4 touches
1 conflict
0x33018431…8f5c
0x188d58…ea8e
4 touches
1 conflict
0x33018431…8f5f
0x188d58…ea8e
4 touches
1 conflict
0x22882eec…bc8a
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0x81550c…bba7
4 touches
1 conflict
0x00000000…0001
0x81550c…bba7
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:
0xb744f5cd…af7777
1 conflict on slot
0x67813250b9…3a9467
Audit this contract →
← previous block
·
next block →
recent activity