pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,224,624
← previous block
next block →
recent activity
Analyzing
Block #76,224,624
11 transactions · 8 stateful · 2026-05-22 08:26:25 UTC
Parallelism
73
/100
Blocked
25
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,224,624
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
updatePrices
#4
0x5bf9264c
#5
0x5bf9264c
#6
0x98717539
· blocks 1
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
· blocks 1
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4548467b…9058
0x34b655…2a6f
4 touches
1 conflict
0x9fc6ea79…e2dc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x27638136…8ca7
0x065c9d…c394
2 touches
0 conflicts
0x33082258…8ab9
0x065c9d…c394
2 touches
0 conflicts
0x3980d8b0…0169
0x065c9d…c394
2 touches
0 conflicts
0xe5ba4022…6380
0x065c9d…c394
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
0x4548467b17…f59058
Audit this contract →
← previous block
·
next block →
recent activity