pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,003,642
← previous block
next block →
recent activity
Analyzing
Block #75,003,642
9 transactions · 8 stateful · 2026-05-16 16:33:00 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,003,642
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xbb5d006a
· blocks 1
#3
updateDataFeedsValuesPartial
#4
withdraw
#5
0x6a089cb3
#6
0xd0278b…2e52
#7
setData
#8
0xaf47a8bb
#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
0x38370fa5…04ae
0x541997…f5a0
4 touches
1 conflict
0x38370fa5…04af
0x541997…f5a0
4 touches
1 conflict
0x02f33632…bfd0
0x541997…f5a0
4 touches
1 conflict
0x915e0c41…095e
0x2e3234…7d90
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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
0x38370fa51d…5104ae
Audit this contract →
← previous block
·
next block →
recent activity