pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,005,423
← previous block
next block →
recent activity
Analyzing
Block #75,005,423
9 transactions · 9 stateful · 2026-05-16 16:44:54 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,005,423
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xbb5d006a
· blocks 1
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x785f5745
#7
0x6a089f7d
#8
setData
#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
0x47747230…35c0
0x541997…f5a0
4 touches
1 conflict
0x24b63caa…efae
0x541997…f5a0
4 touches
1 conflict
0x24b63caa…efaf
0x541997…f5a0
4 touches
1 conflict
0x490911cc…5fea
0x0c65a0…0852
2 touches
0 conflicts
0xef3c5f7a…3127
0x0c65a0…0852
2 touches
0 conflicts
0x2c2761c0…476e
0x34b655…2a6f
2 touches
0 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
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
0x477472301b…3c35c0
Audit this contract →
← previous block
·
next block →
recent activity