pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,204,983
← previous block
next block →
recent activity
Analyzing
Block #75,204,983
7 transactions · 5 stateful · 2026-05-17 14:56:39 UTC
Parallelism
71
/100
Blocked
40
%
Avg conflicts / tx
0.29
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,204,983
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
· blocks 2
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x51a429…2da9
#2
0x98717539
#3
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35b65947…44d1
0xc8689a…ee79
4 touches
1 conflict
0x0fd5f9da…1e9b
0x34b655…2a6f
4 touches
1 conflict
0x3e49348b…9445
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0xcd041b2c…d016
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x74825c4e…32e9
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a4
0x8d66a4…3095
4 touches
1 conflict
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:
0xc8689a47…62ee79
1 conflict on slot
0x35b65947f9…9a44d1
Audit this contract →
← previous block
·
next block →
recent activity