pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,336,907
← previous block
next block →
recent activity
Analyzing
Block #75,336,907
8 transactions · 7 stateful · 2026-05-18 05:39:01 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,336,907
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6a0aa66c
· blocks 1
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x39435dac
· blocks 1
#3
0x6a0aa66c
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b97d40a…09ed
0x34b655…2a6f
4 touches
1 conflict
0xaa3492db…3703
0x34b655…2a6f
4 touches
1 conflict
0xb96e29a5…0419
0x34b655…2a6f
4 touches
1 conflict
0xc3aacf13…6b3d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x37d49489…9309
0x34b655…2a6f
4 touches
1 conflict
0x6c44331f…9735
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
1 conflict on slot
0x7b97d40a0c…6409ed
Audit this contract →
← previous block
·
next block →
recent activity