pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,955,638
← previous block
next block →
recent activity
Analyzing
Block #73,955,638
9 transactions · 7 stateful · 2026-05-11 20:00:00 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,955,638
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
· blocks 1
#2
0x52f07cf9
· blocks 1
#3
0x0c7abd22
#6
0x0f6795d9
#7
setData
#8
0x39435dac
#4
collect
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x10f5f4d8…572e
0x34b655…2a6f
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x20ac0567…c954
0x34b655…2a6f
2 touches
0 conflicts
0x2484cc15…5afc
0x34b655…2a6f
2 touches
0 conflicts
0x2ed00f98…da9f
0x34b655…2a6f
2 touches
0 conflicts
0x35b85d8e…1edd
0x34b655…2a6f
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
0x7cb2f3fa36…384836
Audit this contract →
← previous block
·
next block →
recent activity