pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,901,832
← previous block
next block →
recent activity
Analyzing
Block #75,901,832
9 transactions · 7 stateful · 2026-05-20 20:36:18 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,901,832
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xbb5d006a
· blocks 1
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
0xed82b078
#6
setData
#7
0x39435dac
#8
0x39435dac
#2
0xbb5d006a
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe69c5095…d1e0
0x541997…f5a0
4 touches
1 conflict
0xe69c5095…d1e1
0x541997…f5a0
4 touches
1 conflict
0x5f7786bf…72de
0x541997…f5a0
4 touches
1 conflict
0x10abefc9…c9bc
0x1d1325…2305
2 touches
0 conflicts
0x10d80fee…dbda
0x1d1325…2305
2 touches
0 conflicts
0x3484c9df…bfd5
0x1d1325…2305
2 touches
0 conflicts
0x8cf3d245…1d0d
0x1d1325…2305
2 touches
0 conflicts
0xdb067026…9eb8
0x1d1325…2305
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
0xe69c5095f8…9ed1e0
Audit this contract →
← previous block
·
next block →
recent activity