pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,523,789
← previous block
next block →
recent activity
Analyzing
Block #75,523,789
7 transactions · 5 stateful · 2026-05-19 02:35:30 UTC
Parallelism
71
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,523,789
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6c05cd2b
#2
0x98717539
· blocks 1
#4
0xb9ef3f…75e5
#5
0x6755c7…fa3f
#6
setData
#3
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
2 touches
0 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
2 touches
0 conflicts
0xeb0915f1…c150
0x34b655…2a6f
2 touches
0 conflicts
0xd352f775…a505
0x39b9e0…7777
2 touches
0 conflicts
0xfb1ecd1d…93f8
0x39b9e0…7777
2 touches
0 conflicts
0xb4e825af…69e0
0x3bd359…433a
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:
Perpl
1 conflict on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity