pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,755,405
← previous block
next block →
recent activity
Analyzing
Block #75,755,405
11 transactions · 9 stateful · 2026-05-20 04:19:32 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,755,405
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
dagSwapByOrderId
· blocks 1
#3
0x98717539
#4
0x0c7abd22
#5
updateDataFeedsValuesPartial
#6
send
#7
0x6df9e92b
#8
0x0f6795d9
#9
0x0f6795d9
#10
setData
#2
dagSwapByOrderId
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ef74796…cd18
0x0a3323…0a3c
4 touches
1 conflict
0x00000000…0000
0x834d94…8555
4 touches
1 conflict
0x00000000…0003
0x834d94…8555
4 touches
1 conflict
0x00000000…0004
0x834d94…8555
4 touches
1 conflict
0xa060b594…669d
0x754704…b603
4 touches
1 conflict
0x7467907b…964b
0x0a3323…0a3c
2 touches
0 conflicts
0xb1632c2f…d991
0x0a3323…0a3c
2 touches
0 conflicts
0xdeaab6a3…ccad
0x0a3323…0a3c
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:
0x0a332311…6e0a3c
1 conflict on slot
0x0ef74796d8…7ccd18
Audit this contract →
← previous block
·
next block →
recent activity