pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,833,461
← previous block
next block →
recent activity
Analyzing
Block #75,833,461
8 transactions · 7 stateful · 2026-05-20 12:59:29 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,833,461
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
dagSwapByOrderId
· blocks 1
#3
0x98717539
· blocks 1
#4
updateDataFeedsValuesPartial
#5
setData
#7
0x39435dac
#2
dagSwapByOrderId
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x451e482b…7e7d
0x34b655…2a6f
4 touches
1 conflict
0xd06cc746…27e4
0x384275…7777
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x16b3ffeb…cca1
0x188d58…ea8e
2 touches
0 conflicts
0x16b3ffeb…cca2
0x188d58…ea8e
2 touches
0 conflicts
0x40c0484d…8192
0x188d58…ea8e
2 touches
0 conflicts
0x40c0484d…8194
0x188d58…ea8e
2 touches
0 conflicts
0x7c81204d…1f5b
0x384275…7777
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:
Perpl
1 conflict on slot
0x451e482b59…427e7d
Audit this contract →
← previous block
·
next block →
recent activity