pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,833,645
← previous block
next block →
recent activity
Analyzing
Block #75,833,645
14 transactions · 11 stateful · 2026-05-20 13:00:44 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,833,645
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swap
#2
dagSwapByOrderId
#3
0x4d8dc985
· blocks 1
#4
initialize
#5
initialize
#6
0x0f6795d9
#7
0x0f6795d9
#8
updateDataFeedsValuesPartial
#9
0x6a0db0f4
#10
0xeb8ce755
#11
setData
#13
0x39435dac
#12
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x139aab…382b
2 touches
0 conflicts
0x00000000…0001
0x139aab…382b
2 touches
0 conflicts
0x00000000…0003
0x139aab…382b
2 touches
0 conflicts
0x00000000…000e
0x139aab…382b
2 touches
0 conflicts
0xa2056a0b…a4fc
0x188d58…ea8e
2 touches
0 conflicts
0xa2056a0b…a4fd
0x188d58…ea8e
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity