pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,014,684
← previous block
next block →
recent activity
Analyzing
Block #75,014,684
11 transactions · 8 stateful · 2026-05-16 17:46:46 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,014,684
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
_makeSwaps
#2
0x5bf9264c
#3
0x5bf9264c
#4
0x1a945f9c
· blocks 1
#5
updateDataFeedsValuesPartial
#7
0xb55e36…91fe
#8
0xd1aaab…2a6f
#9
setData
#10
0x39435dac
#6
0xd10227eb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xc93402b9…746d
0x000000…8ba3
2 touches
0 conflicts
0x18e93da3…5d91
0x0555e3…2b9c
2 touches
0 conflicts
0x62e20208…be65
0x0555e3…2b9c
2 touches
0 conflicts
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0xf9fbc006…eb42
0x065c9d…c394
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:
LeverUp: LeverUp
1 conflict on slot
0xa8abcc1955…203d83
Audit this contract →
← previous block
·
next block →
recent activity