pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,730,816
← previous block
next block →
recent activity
Analyzing
Block #75,730,816
11 transactions · 10 stateful · 2026-05-20 01:36:00 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,730,816
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a0d1077
#2
0x0c7abd22
#3
0x0f6795d9
#4
0x0f6795d9
#5
setData
#6
0x39435dac
· blocks 1
#8
0x39435dac
#9
0x39435dac
#10
0x39435dac
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d34f2bd…5d63
0x34b655…2a6f
4 touches
1 conflict
0x615bc8cc…15d2
0x34b655…2a6f
4 touches
1 conflict
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0xcef70a96…db44
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfbabb02d…af07
0x34b655…2a6f
4 touches
1 conflict
0xfefd1e1d…5fed
0x34b655…2a6f
4 touches
1 conflict
0x03b4fefa…9a00
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
0x3d34f2bde7…d05d63
Audit this contract →
← previous block
·
next block →
recent activity