pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,514,256
← previous block
next block →
recent activity
Analyzing
Block #74,514,256
8 transactions · 6 stateful · 2026-05-14 10:00:10 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,514,256
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xf99cae99
· blocks 1
#2
0xed82b078
#4
0x0c7abd22
#5
updateDataFeedsValuesPartial
#6
0x1a15fe…c20f
#7
setData
#3
0x5de3085d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x536e2740…61ac
0x3bd359…433a
4 touches
1 conflict
0x00000000…0002
0xa7283d…0ace
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x968bdacb…f461
0x2a68ba…90c5
2 touches
0 conflicts
0x99761a60…872c
0xa68a7f…352c
2 touches
0 conflicts
0x95fa6aba…eec1
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
1 conflict on slot
0x536e2740da…e461ac
Audit this contract →
← previous block
·
next block →
recent activity