pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,683,656
← previous block
next block →
recent activity
Analyzing
Block #71,683,656
21 transactions · 16 stateful · 2026-05-01 07:29:32 UTC
Parallelism
57
/100
Blocked
56
%
Avg conflicts / tx
1.76
Longest chain
9
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,683,656
· 21 txs across 9 waves · depth 9
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
#0
syscallReward
#1
0x0c7abd22
· blocks 9
#7
execute
#9
0x05ee6a22
#10
execute
#12
0xeffdedb0
#14
updateDataFeedsValuesPartial
#16
0x6df9e92b
#17
createModule
#18
setData
#19
0x39435dac
#20
jMMeC
#2
0x0c7abd22
· blocks 7
#15
0x3f5c179b
#3
0x0c7abd22
· blocks 6
#4
0x0c7abd22
· blocks 5
#5
0x0c7abd22
· blocks 4
#6
0x0c7abd22
· blocks 3
#8
0x0c7abd22
· blocks 2
#11
0x0c7abd22
· blocks 1
#13
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
5
w4
6
w5
8
w6
11
w7
13
w8
15
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d07c8b3…b9ee
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x91945265…e58f
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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:
0xd32edf66…9fff58
36 conflicts on slot
0x0d07c8b351…65b9ee
Audit this contract →
← previous block
·
next block →
recent activity