pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,847,573
← previous block
next block →
recent activity
Analyzing
Block #75,847,573
8 transactions · 6 stateful · 2026-05-20 14:34:25 UTC
Parallelism
75
/100
Blocked
33
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,847,573
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
0x98717539
· blocks 1
#4
collect
#6
updateDataFeedsValuesPartial
#7
setData
#3
0x98717539
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa94cf3f4…554c
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a4
0x8d66a4…3095
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x904fc3c0…00ec
0x34b655…2a6f
4 touches
1 conflict
0x74825c4e…32e9
0x8d66a4…3095
4 touches
1 conflict
0xa48ec0df…51fb
0x065c9d…c394
3 touches
1 conflict
0x8a35acfb…d1a7
0x8d66a4…3095
3 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:
0x8d66a43f…113095
1 conflict on slot
0xa94cf3f4f8…4d554c
Audit this contract →
← previous block
·
next block →
recent activity