pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,091,672
← previous block
next block →
recent activity
Analyzing
Block #75,091,672
12 transactions · 11 stateful · 2026-05-17 02:20:19 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,091,672
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x39abec6b
#3
forward
#4
0x6a09265b
#5
setData
#6
0x39435dac
#7
0x39435dac
#8
0x39435dac
#9
0x39435dac
· blocks 1
#10
0x39435dac
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf06c2cf5…61bd
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x047d8971…c728
0x2ab50b…5c41
2 touches
0 conflicts
0x0be70560…c7e7
0x2ab50b…5c41
2 touches
0 conflicts
0x1035ed1e…3885
0x2ab50b…5c41
2 touches
0 conflicts
0x13699c33…f787
0x2ab50b…5c41
2 touches
0 conflicts
0x15a8b5e6…0296
0x2ab50b…5c41
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:
Perpl
1 conflict on slot
0xf06c2cf5e4…3161bd
Audit this contract →
← previous block
·
next block →
recent activity