pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,865,403
← previous block
next block →
recent activity
Analyzing
Block #75,865,403
9 transactions · 9 stateful · 2026-05-20 16:33:50 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,865,403
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x98717539
· blocks 1
#2
updateDataFeedsValuesPartial
#3
setData
#4
0x6df9e92b
· blocks 1
#7
withdrawCollateral
#5
0x6df9e92b
#6
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
6
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44ad89ba…cf83
0x23c26b…7777
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x81a7ba4d…8c4b
0x23c26b…7777
4 touches
1 conflict
0x11e1e2a4…54fb
0x34b655…2a6f
4 touches
1 conflict
0x08fdca0b…4abf
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x451e482b…7e7d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0xfdc9ea…8789
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:
Mouch (MOUCH)
1 conflict on slot
0x44ad89ba62…49cf83
Audit this contract →
← previous block
·
next block →
recent activity