pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,973,447
← previous block
next block →
recent activity
Analyzing
Block #72,973,447
10 transactions · 9 stateful · 2026-05-07 06:47:45 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,973,447
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab795ed3
#2
postState
#3
0xb264ae19
#4
0xed82b078
#5
setData
#6
0x69fc3609
#7
0x98717539
· blocks 1
#8
0xeffdedb0
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0x388e001a…7e04
0x34b655…2a6f
4 touches
1 conflict
0x7cbd466f…1700
0x34b655…2a6f
4 touches
1 conflict
0xe7574014…95e2
0x34b655…2a6f
4 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
2 touches
0 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0005
0x2a3755…a5a6
2 touches
0 conflicts
0xe870e232…7369
0x2a3755…a5a6
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
0xf853eb8e72…d84027
Audit this contract →
← previous block
·
next block →
recent activity