pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,527,110
← previous block
next block →
recent activity
Analyzing
Block #74,527,110
11 transactions · 10 stateful · 2026-05-14 11:26:44 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,527,110
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
· blocks 2
#2
updatePrices
#3
exec
#4
updateFeeds
#5
updateDataFeedsValuesPartial
#8
0xeb8ce755
#9
setData
#10
0x39435dac
#6
0x5339c59f
#7
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1a59ab4…eca9
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0xa3c3aa74…f2d7
0x065c9d…c394
3 touches
1 conflict
0xf1f08334…fa5b
0x065c9d…c394
3 touches
1 conflict
0x49cbc8bf…898f
0x065c9d…c394
3 touches
1 conflict
0x26fc9d73…9d87
0x065c9d…c394
3 touches
1 conflict
0x30276c1c…47b4
0x2a68ba…90c5
2 touches
0 conflicts
0x765c236f…ff45
0x2a68ba…90c5
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:
0x065c9d28…a9c394
1 conflict on slot
0xa1a59ab49f…beeca9
Audit this contract →
← previous block
·
next block →
recent activity