pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,630,805
← previous block
next block →
recent activity
Analyzing
Block #74,630,805
8 transactions · 8 stateful · 2026-05-14 23:02:46 UTC
Parallelism
63
/100
Blocked
25
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,630,805
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x98717539
· blocks 2
#4
updateDataFeedsValuesPartial
#5
quoteUpdate
#6
0x6a06550d
#7
setData
#2
0x98717539
· blocks 1
#3
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x8d66a4…3095
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1a0
0x8d66a4…3095
6 touches
3 conflicts
0x8a35acfb…d1a1
0x8d66a4…3095
6 touches
3 conflicts
0x9abd5cd0…9d1d
0x8d66a4…3095
5 touches
3 conflicts
0x8a35acfb…d1a2
0x8d66a4…3095
5 touches
3 conflicts
0xeb0915f1…c150
0x34b655…2a6f
4 touches
1 conflict
0x2fad73a1…ae09
0x34b655…2a6f
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:
0x8d66a43f…113095
3 conflicts on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity