pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,702,513
← previous block
next block →
recent activity
Analyzing
Block #75,702,513
11 transactions · 7 stateful · 2026-05-19 22:27:27 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,702,513
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe0de3ed7
#2
updateDataFeedsValuesPartial
#3
0x98717539
#4
0xe705c0…fdf7
#5
0x0c7abd22
· blocks 1
#6
setData
#7
0x39435dac
#9
jMMeC
#10
jMMeC
#8
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x784b1c95…87cc
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x04c70b12…1178
0x34b655…2a6f
2 touches
0 conflicts
0x14c20295…4d9e
0x34b655…2a6f
2 touches
0 conflicts
0x37be28df…a4e0
0x34b655…2a6f
2 touches
0 conflicts
0x4118bd12…924a
0x34b655…2a6f
2 touches
0 conflicts
0x4ec9ff52…e6f7
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:
FastLane: FastLaneAuctionHandler
1 conflict on slot
0x784b1c95d3…6187cc
Audit this contract →
← previous block
·
next block →
recent activity