pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,767,932
← previous block
next block →
recent activity
Analyzing
Block #74,767,932
10 transactions · 8 stateful · 2026-05-15 14:18:13 UTC
Parallelism
70
/100
Blocked
38
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,767,932
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6df9e92b
· blocks 2
#2
0x98717539
· blocks 1
#3
updateDataFeedsValuesPartial
#5
0xed82b078
#8
setData
#9
withdraw
#4
0x39435dac
#6
0x6df9e92b
· blocks 1
#7
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w1
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0x67813250…9467
0xb744f5…7777
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x22882eec…bc8a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x81550c…bba7
4 touches
1 conflict
0x00000000…0001
0x81550c…bba7
4 touches
1 conflict
0x44ad89ba…cf83
0xb744f5…7777
4 touches
1 conflict
0xe7c88fe0…9f10
0xa7283d…0ace
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:
0x3bd359c1…15433a
3 conflicts on slot
0xa472d565a0…ae9fe4
Audit this contract →
← previous block
·
next block →
recent activity