pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,286,044
← previous block
next block →
recent activity
Analyzing
Block #72,286,044
12 transactions · 9 stateful · 2026-05-04 02:27:27 UTC
Parallelism
83
/100
Blocked
33
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,286,044
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
0x1094dc9f
#5
0x5bf9264c
#6
0x5bf9264c
#7
0x3f5c179b
#8
setData
#9
0x39435dac
· blocks 1
#11
0x39435dac
#2
0x0c7abd22
#4
execute
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x729c91b8…9537
0x188d58…ea8e
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x729c91b8…9539
0x188d58…ea8e
4 touches
1 conflict
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x1ec773b0…8e63
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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:
0x188d586d…f9ea8e
1 conflict on slot
0x729c91b8a3…e19537
Audit this contract →
← previous block
·
next block →
recent activity