pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,702,713
← previous block
next block →
recent activity
Analyzing
Block #75,702,713
9 transactions · 6 stateful · 2026-05-19 22:28:47 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,702,713
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
0x98717539
· blocks 1
#5
setData
#6
updateDataFeedsValuesPartial
#7
0x0f3fbf…8894
#8
0x7e0422…a3d3
#4
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35b65947…44d1
0xc8689a…ee79
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x422d5490…52d9
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x674c1ed4…da3f
0x34b655…2a6f
4 touches
1 conflict
0x6d5df434…ba93
0x34b655…2a6f
4 touches
1 conflict
0x75f928fc…0465
0x34b655…2a6f
4 touches
1 conflict
0xa8bd52b5…862e
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:
Perpl: Settlement / Helper
1 conflict on slot
0x35b65947f9…9a44d1
Audit this contract →
← previous block
·
next block →
recent activity