pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,231,423
← previous block
next block →
recent activity
Analyzing
Block #75,231,423
11 transactions · 8 stateful · 2026-05-17 17:53:13 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,231,423
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a0a0101
#2
0x98717539
#3
0xed82b078
#4
0x6df9e92b
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x5339c59f
#9
0x6a0a0101
#10
setData
#5
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x86dfd5…6a7d
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x1686502b…a1d2
0x3bd359…433a
4 touches
1 conflict
0x1d4c90ab…1ba7
0xb72e62…7777
4 touches
1 conflict
0x44ad89ba…cf83
0xb72e62…7777
4 touches
1 conflict
0x00000000…0000
0x86dfd5…6a7d
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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:
0x86dfd554…906a7d
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity