pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,215,363
← previous block
next block →
recent activity
Analyzing
Block #74,215,363
25 transactions · 18 stateful · 2026-05-13 00:50:31 UTC
Parallelism
84
/100
Blocked
39
%
Avg conflicts / tx
0.44
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,215,363
· 25 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execute_route
· blocks 1
#2
0xb264ae19
#3
0xcf7468f4
#4
0x1094dc9f
#5
execute
#7
execute
#8
0xed82b078
· blocks 3
#10
0xe7be4706
#11
0x5bf9264c
#12
0x5bf9264c
#13
0xe7be4706
#14
0x98717539
· blocks 2
#15
updateDataFeedsValuesPartial
#16
0x0c7abd22
#18
0xed82b078
#21
0xed82b078
#22
setData
#6
exactOutputSingle
#9
0xed82b078
· blocks 3
#23
0x39435dac
· blocks 1
#17
0x5339c59f
#19
0xed82b078
· blocks 1
#24
0x39435dac
#20
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
8
w0
9
w1
14
w0
17
w2
19
w2
20
w3
23
w1
24
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x768cffcd…2648
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0004
0xd5b70d…615b
4 touches
1 conflict
0x18aed20c…48f3
0x000000…012a
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xeea3f128…72db
0x34b655…2a6f
4 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
4 touches
1 conflict
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:
0x065c9d28…a9c394
6 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity