pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,947,129
← previous block
next block →
recent activity
Analyzing
Block #75,947,129
10 transactions · 9 stateful · 2026-05-21 01:37:48 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,947,129
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
0xbb5d006a
· blocks 1
#4
0xb5ce855a
#5
0xab083028
#6
0x98717539
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
#3
0xbb5d006a
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
0x1c3a9b45…4a77
0x541997…f5a0
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x6bd9b2de…7d72
0x0f2610…0edc
2 touches
0 conflicts
0x78c09e1a…89ad
0x2185cd…21c7
2 touches
0 conflicts
0x192a5abc…fae0
0x2ae0cf…3d4e
2 touches
0 conflicts
0x233173c8…871f
0x2ae0cf…3d4e
2 touches
0 conflicts
0x384d192f…7782
0x2ae0cf…3d4e
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:
0x541997e9…30f5a0
1 conflict on slot
0x1c3a9b45de…bb4a77
Audit this contract →
← previous block
·
next block →
recent activity